So often as developers do we sit down and go “I can do this better”, then File –> New. With so many awesome open source projects, shouldn’t we be doing a “git clone” instead and submitting pull requests?
I have been guilty of this forever, and I think most windows developers have.
I have been using MSTest forever for Unit Testing, the last time I used nUnit I created a video tutorial on how to set it up circa 2005, that somehow still gets a ton of views, and my oh my how I have changed since that video.
However, I ran across a recent blog post from Rob Conery that showed a really nice for A Simple Approach to BDD. In the article he talks about how he just used xUnit for his unit testing with good naming to have a BDD like approach for his test results.
Among the thousands of other developers, I have jumped onto the Elasticsearch fan base.
Elasticsearch is a flexible and powerful open source, distributed, real-time search and analytics engine. Architected from the ground up for use in distributed environments where reliability and scalability are must haves, Elasticsearch gives you the ability to move easily beyond simple full-text search.
I have been working with Elasticsearch for just under a year now, and I have a pretty good understanding of building queries, templates, facets, and aggregations. About three months ago I switched off of Couchbase+Elasticsearch to just Elasticsearch to “skip the middle man”. Elasticsearch is a powerful document store, it is fast, supports versioning as well as partial and scripted updates.
So let’s talk about the .Net clients that are available for Elasticsearch. There are a few out there, and they have their benefits.
