What users are saying about
28 Ratings
93 Ratings
28 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.2 out of 101
93 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.9 out of 101

Add comparison

Likelihood to Recommend

Apache Solr

Very effective for end-user searching applications and for generating search results. Also very well suited to those looking for high reliability and performance. If [you're doing] fuzzy searching or if you are working on a smaller end-user application or an internal application that does not require high performance and flexible/adapting searching then it may not be necessary to use Solr.
No photo available

Elasticsearch

Elasticsearch is the gold standard for text-based search. Across large data sets it performs admirably, and we will certainly make it our first choice search solution in the future. For a use case where needs are simple and regular database queries might suffice, Elasticsearch may or may not provide any benefits.
No photo available

Pros

  • Faceted navigation and field collapsing/grouping : filtering and quick results were what we needed for our websites. Our customers needed to have this functionalities for good and efficient results.
  • We tested them with our customers' registered searches (they received all new goods matching with their registered searches by emails and/or mobile push). Results were incredible by comparison with our old system (old MySQL requests).
  • Note : we didn't put all our data in Solr. Just what we need for searching uses. Other data stayed in our MySQL database.
  • Auto-suggest : our old auto-suggest wasn't performing well. With Apache Solr, our new one was worked really well ! The suggestions came quickly and suggestions were good.
  • We also extended auto-suggestion with geo-spatial data and it worked well.
  • Hit highlighting : we used this functionality and we didn't have problem and nasty surprise.
  • Keep all data status during data upgrading (see next details for improvements)
Philippe Kozak profile photo
  • Lightning fast
  • Easily scalable
  • Powerful feature set
No photo available

Cons

  • Version 4.3-4.10, the documentation for Solr was very lacking.
  • No monitoring for Solr available built-in; have to be dependent on CDH or HDP if you are implementing thru them.
  • CPU consumption can be high in some cases.
Bharadwaj (Brad) Chivukula profile photo
  • Setting Java memory thresholds can be a pain for those not accustomed to things like Eden Space & Old Generation which can lead to over allocation, or more likely, under allocation. Apache Solr had a similar issue. It would be nice if the program would take an extra step and dogfood it's own advice by analyzing the system & processes to return a solid recommendation for that configuration. The proper configuration information is outlined in the documentation, it would be nice if that was automated.
  • The only health check that ElasticSearch reports back is a "red" status without any real solid information about what is going on, though its usually memory thresholds or disk I/O. I am currently on ElasticSearch 1.5 so that may have changed for newer versions. When the status goes "red", I as the administrator of the software, feel like I lose control of whats going on which should rarely happen. Something more verbose would eliminate that.
  • This is more of a critique of the ElasticStack in general. The whole top to bottom stack is starting to get feature creep with things that are better suited in other software and increasing the barrier for entry for people to get started with setting up a robust logging infrastructure. ElasticSearch as a storage search engine, is pretty streamlined, but I can see that the tools that comprise the ELK Stack are going to require a certification with constant study at some point. During major release for Logstash a while back, it literally took a month to learn a new language because Elastic completely changed the syntax. For a medium sized organization of only a couple of admins, that is a pretty high bar where time is money. They really should work on refining/automating the tools & search engine they have, instead of shoehorning/changing things on to an already rock solid foundation.
Colby Shores profile photo

Likelihood to Renew

No score
No answers yet
No answers on this topic
Elasticsearch10.0
Based on 1 answer
We're pretty heavily invested in ElasticSearch at this point, and there aren't any obvious negatives that would make us reconsider this decision.
Aaron Gussman profile photo

Usability

No score
No answers yet
No answers on this topic
Elasticsearch10.0
Based on 1 answer
To get started with Elasticsearch, you don't have to get very involved in configuring what really is an incredibly complex system under the hood. You simply install the package, run the service, and you're immediately able to begin using it. You don't need to learn any sort of query language to add data to Elasticsearch or perform some basic searching.If you're used to any sort of RESTful API, getting started with Elasticsearch is a breeze. If you've never interacted with a RESTful API directly, the journey may be a little more bumpy. Overall, though, it's incredibly simple to use for what it's doing under the covers.
No photo available

Implementation

No score
No answers yet
No answers on this topic
Elasticsearch9.0
Based on 1 answer
Do not mix data and master roles. Dedicate at least 3 nodes just for Master
No photo available

Alternatives Considered

Between Solr and ElasticSearch, there is a constant struggle to pick the best one. ElasticSearch is part of ELK and ties in well with LogStash and Kibana which makes it great for logs and big data stuff. Add some logs and see which works best for your particular access methods and queries. They are very similar but elasticsearch is better for REST access.
Bharadwaj (Brad) Chivukula profile photo
ElasticSearch was easier to scale and faster than Mongo.
Aaron Gussman profile photo

Return on Investment

  • Usage of Solr in the browse webpages (apart from Search) has resulted in customer choosing his/her product within 3 clicks by the using of faceting.
  • Speed, relevance and efficiency of search results.
  • Using Solr for International Markets comes out of box.
Bharadwaj (Brad) Chivukula profile photo
  • Improved the speed of our website
  • Improved the user experience by providing highly efficient text search
  • We're using it for logging, which makes it easy to query the errors and solve them
  • It takes time to understand the advanced queries in Elasticsearch
Tarun Mangukiya profile photo

Pricing Details

Apache Solr

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details

Elasticsearch

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details