You're starting from the wrong place if you're comparing Elasticsearch with a database. And you're also arriving at the wrong place if you think that any database can be distributed.
"Elasticsearch is a distributed, free and open search and analytics engine for all types of data, including textual, numerical, geospatial, structured, and unstructured. Elasticsearch is built on Apache Lucene and was first released in 2010..."
I suggest understanding what it is first before comparing it to other databases.
Elastic gives you a lot of the fancy stuff that SQL kinda needs extras and hard work for... but it's just a document store with fancy weighting features.
Elasticsearch is a no-sql database that optimizes for full-text searches, built atop Apache Lucene. If you're doing any kind of full-text search, for example, if you're trying to index a university library and make it searchable, then elasticsearch is for you. If you're not, I'd look elsewhere.
On their home page, "Why use Elastic search?", the reasons are basically:
* It's fast!
* It does a lot of stuff!
* It has some tools to visualize data!
* It's distributed!!
I have to say this is not very appealing to me since it sounds like something any database could do.