Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Elasticsearch Moved Into the Top 10 Most Popular Database Management Systems

DZone's Guide to

Elasticsearch Moved Into the Top 10 Most Popular Database Management Systems

The steady growth in its popularity as measured by our popularity score is really impressive — they started with a score of 7.4 and are now at 115.98.

· Database Zone ·
Free Resource

Compliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper

Elasticsearch has seen a steady growth in popularity over the last several years. It is now not only the most popular enterprise search engine but it is also one of the 10 most popular database management systems.

We started to monitor Elasticsearch's popularity more than four years ago. In these four years, Elasticsearch became the most popular search engine and it was one of the top three systems in our DBMS of the Year Award in 2014. The steady growth in its popularity as measured by our popularity score is really impressive — they started with a score of 7.4 and are now at 115.98. This is a 15-fold increase in our ranking components such as mentions in job offers, in LinkedIn profiles, in Google Trends, or in activity on Stackoverflow. Elasticsearch was at rank 21 four years ago in our DB-Engines Ranking, and it is now the first search engine in the top 10.

search engines popularity

Popularity trend of top search engines.

There is no shortage of strong competitors in the enterprise search engine market. There's Solr, the former #1, based on Apache Lucene just like Elasticsearch. Then we have Splunk, MarkLogic, and many others. Despite all of this competition, Elasticsearch managed to be used in some of the most complex and prestigious projects: Wikipedia is using Elasticsearch, and so are eBay, Yelp, and Netflix.

But Elastic, the company behind Elasticsearch, has ambitions that go further than pure search technology. They have developed the Elastic Stack around its search component, which includes Beats and Logstash for data collection and Kibana for data visualization. This tool set is often used for log search and analysis, thus moving beyond the traditional search engine market, while still using Elasticsearch as its key component.

Elastic also puts a strong focus on the growing DBaaS market: they offer their own Elasticsearch-As-A-Service cloud solution, but there is also Amazon Elasticsearch Service and Google announced to offer the Elastic Cloud product on their Google Cloud Platform later this year. In addition to that, Elastic keeps acquiring startups in various fields, most recently they made efforts to add machine learning into their product portfolio. Such a strategy is certainly not without risks, but so far, Elastic seems to manage their challenges quite well.

We will keep an eye on that product to see whether they can go beyond what they already achieved.

Compliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper

Topics:
database ,elasticsearch ,rdbms ,search engine

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}