Elasticsearch Joins Fog Creek
April 8, 2013
Elasticsearch is trying to expand its reach by partnering with other trendy tech services. It is definitely getting some headlines. The most recent headline is detailed by Market Watch in their article, “Fog Creek Selects Elasticsearch to Search and Analyze Terabytes of Data.”
“Elasticsearch, the company behind the popular real-time search and analytics open source project, today announced that Fog Creek has selected Elasticsearch to provide instant search capabilities within Kiln, its software development product. Kiln is designed to support and simplify development workflow for users searching more than 100,000 source code repositories. Elasticsearch is now a critical ingredient of Kiln, providing instant search for 300,000,000 requests across 40 billion lines of code to improve overall performance, reliability and user experience.”
Elasticsearch is known for collaboration with leading edge products, but it is not without its controversies as well. GitHub recently reached out to Elasticsearch to develop its new search infrastructure, but the service quickly exposed security concerns and then crashed. So when it comes to a search infrastructure that goes beyond trends, trust an industry standard. Do not assume that every search application will be safe enough for the enterprise. For instance, consider LucidWorks. They are built on open source Lucene/Solr, employ one quarter of the Core Committers on that project, and are optimized for the enterprise. Choose industry confidence, not trends.
Emily Rae Aldridge, April 8, 2013
Sponsored by ArnoldIT.com, developer of Beyond Search
Comments
One Response to “Elasticsearch Joins Fog Creek”
-
- Subscribe to Beyond Search
Feature archive
News archive
-
I’m sorry you’re wrong here. Github chose to use Elasticsearch software to power their search feature, which when launched exposed poor security on the part of their users (who had left passwords in plain text). They then had some scaling issues and at this point asked the authors of Elasticsearch to help – and got it fixed. You can read the story here. https://github.com/blog/1397-recent-code-search-outages