Geek Answers Handbook

What are the pros and cons of Solr & ElasticSearch?

Both Solr and ElasticSearch are built on Lucene.

How do they compare to each other in terms of:

  • Features (in particular, facet support and multilingualism)
  • Performance
  • Scalability
  • Sustainability
  • Controllability

Any experience you have with any software you can provide?

Thanks.

+7
source share
2 answers

Well, make it short and simple:

  • Use SOLR if you want to be able to fine-tune your performance (getting confused by internal components), want more control, as well as a huge community.

  • Use elastic search if you need a faster deployment, ready to live with less control (there are additional options) and get the actual result (during development) that you want to get during deployment.

Known as scalable and stable, they offer great performance .

PS: I read that a person is "stuck" with some minor problems / errors in the elastic search . However, there are many that are satisfied .: D

+8
source

I can only talk about Solr, as this is what we use.

I deployed the Solr stack to EC2 and we process several million records in each database. I currently have a master / slave setup and a very good circuit.

Beyond the obvious benefits of Solr and the awesome queries you can do, one thing that is often overlooked is how easy it is to set up and learn! It took me a day to read the Solr 1.4 Enterprise Search Server, and a week later I built a fairly robust Master and Slave AMI on Amazon EC2, performed load testing and configured Map Reduce jobs to continuously pump data into Solr Master.

My two cents.

+4
source

More articles:


All Articles