What users are saying about
35 Ratings
Top Rated
154 Ratings
35 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 7.7 out of 100
Top Rated
154 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.7 out of 100

Highlights

Apache Solr and Elasticsearch are both open-source enterprise search software solutions that allow users to search and retrieve data within an organization. Both software options integrate with tools like databases or intranets where information can be collected or displayed. Businesses of all sizes use both Apache Solr and Elasticsearch.

Features

Apache Solr and Elasticsearch both provide essential enterprise search features, including data retrieval and display. Despite this, both software options have a few standout features that set them apart from each other.

Apache Solr offers robust text search features that allow users to search for materials by their content. Apache Solr has many contributors to its open-source code. Developers and code committers for Apache Solr are selected from that community of contributors. This approach to development means bugfixes and updates are frequent, and features can be developed quickly. Lastly, Apache Solr provides detailed documentation for developers, including multiple examples.

Elasticsearch is lightweight to the extent that a business can install and run the Elasticsearch in a matter of minutes. Similarly, Elasticsearch configuration is based on JSON, which makes file configuration simple, if a little inflexible in terms of documentation. JSON compatibility also makes Elasticsearch a great choice when working with JSON applications. Elasticsearch focuses on complex querying and filtering, though it also offers basic text search. Lastly, Elasticsearch is designed for the cloud and supports clustering, leading to a highly scalable option.

Limitations

Though Apache Solr and Elasticsearch have robust sets of features, they both have a few limitations that are important to consider.

Apache Solr offers text search features but is limited when it comes to more complex querying and filtering. Lack of complex querying can make Apache Solr a poor choice for applications that need non-text search features. Additionally, Apache Solr is a heavier software option compared to Elasticsearch, which can make installation more challenging for lightweight applications.

Elasticsearch is open-source in that all users have access to the source code. However, unlike many open-source technologies, all changes to the code must be approved by Elastic developers. As a result, Elasticsearch provides the financial benefits of open-source software but doesn’t offer the same level of community development as Apache Solr. Additionally, though Elastisearch provides complex search features, its text search features are more limited compared to Apache Solr.

Pricing

Apache Solr and Elasticsearch are both open-source technologies, meaning their source code is available for free. Despite this, both software options also have vendors that provide cloud hosting services. Pricing for Apache Solr and Elasticsearch is dependent on factors such as the vendor, support needs, and amount of indexed nodes. Apache Solr pricing usually starts around $10.00 per month, while Elasticsearch starts around $16.00 per month.

Likelihood to Recommend

Apache Solr

Solr spins up nicely and works effectively for small enterprise environments providing helpful mechanisms for fuzzy searches and facetted searching. For larger enterprises with complex business solutions you'll find the need to hire an expert Solr engineer to optimize the powerful platform to your needs.Internationalization is tricky with Solr and many hosting solutions may limit you to a latin character set.
Peter Feddo | TrustRadius Reviewer

Elasticsearch

Elasticsearch's best use case is when you want to store loosely-structured data and be able to search for it near-instantly. And you want to do that in a highly tolerant distributed system. My company doesn't use it this way but I've heard of other companies using ES to store system logs. Another company uses it to store giant store-catalogs.
Anonymous | TrustRadius Reviewer

Pros

Apache Solr

  • Easy to get started with Apache Solr. Whether it is tackling a setup issue or trying to learn some of the more advanced features, there are plenty of resources to help you out and get you going.
  • Performance. Apache Solr allows for a lot of custom tuning (if needed) and provides great out of the box performance for searching on large data sets.
  • Maintenance. After setting up Solr in a production environment there are plenty of tools provided to help you maintain and update your application. Apache Solr comes with great fault tolerance built in and has proven to be very reliable.
Anonymous | TrustRadius Reviewer

Elasticsearch

  • Super-fast search on millions of documents. We've got over 2 billion documents in our index and the retrieve speeds are still in the < 1-second range.
  • Analytics on top of your search. If you organize your data appropriately, Elasticsearch can serve as a distributed OLAP system
  • Elasticsearch is great for geographic data as well, including searching and filtering with geojson, and a variety of geospatial algorithms.
Anatoly Geyfman | TrustRadius Reviewer

Cons

Apache Solr

  • These examples are due to the way we use Apache Solr. I think we have had the same problems with other NoSQL databases (but perhaps not the same solution). High data volumes of data and a lot of users were the causes.
  • We have lot of classifications and lot of data for each classification. This gave us several problems:
  • First: We couldn't keep all our data in Solr. Then we have all data in our MySQL DB and searching data in Solr. So we need to be sure to update and match the 2 databases in the same time.
  • Second: We needed several load balanced Solr databases.
  • Third: We needed to update all the databases and keep old data status.
  • If I don't speak about problems due to our lack of experience, the main Solr problem came from frequency of updates vs validation of several database. We encountered several locks due to this (our ops team didn't want to use real clustering, so all DB weren't updated). Problem messages were not always clear and we several days to understand the problems.
Philippe Kozak | TrustRadius Reviewer

Elasticsearch

  • 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 | TrustRadius Reviewer

Likelihood to Renew

Apache Solr

No score
No answers yet
No answers on this topic

Elasticsearch

Elasticsearch 10.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 | TrustRadius Reviewer

Usability

Apache Solr

No score
No answers yet
No answers on this topic

Elasticsearch

Elasticsearch 10.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.
Anonymous | TrustRadius Reviewer

Support Rating

Apache Solr

No score
No answers yet
No answers on this topic

Elasticsearch

Elasticsearch 7.5
Based on 12 answers
We've only used it as an opensource tooling. We did not purchase any additional support to roll out the elasticsearch software. When rolling out the application on our platform we've used the documentation which was available online. During our test phases we did not experience any bugs or issues so we did not rely on support at all.
Anonymous | TrustRadius Reviewer

Implementation Rating

Apache Solr

No score
No answers yet
No answers on this topic

Elasticsearch

Elasticsearch 9.0
Based on 1 answer
Do not mix data and master roles. Dedicate at least 3 nodes just for Master
Anonymous | TrustRadius Reviewer

Alternatives Considered

Apache Solr

We have considering AWS search and Elastic search but decide to go with Solr as we need high speed and flexible query, and so far it meets all our requirement so we still continue with Solr.
trang nguyen | TrustRadius Reviewer

Elasticsearch

As far as we are concerned, Elasticsearch is the gold standard and we have barely evaluated any alternatives. You could consider it an alternative to a relational or NoSQL database, so in cases where those suffice, you don't need Elasticsearch. But if you want powerful text-based search capabilities across large data sets, Elasticsearch is the way to go.
Anonymous | TrustRadius Reviewer

Return on Investment

Apache Solr

  • It's enabled us to deliver fast, relevant search results on our new website. The site is still in beta and being actively developed so our complete ROI is still unknown.
  • It integrates very well with Drupal so it has saved us from having to develop a custom solution.
Richard Davies | TrustRadius Reviewer

Elasticsearch

  • Faster searches on our application have resulted in better usability and increased application use
  • Analytics dashboard has given our managers a better understanding of day-to-day activities
  • Being a backup data store, we need not touch SQL database while doing data dumps for local data science projects
Swastik Nath | TrustRadius Reviewer

Pricing Details

Apache Solr

General

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

Apache Solr Editions & Modules

Additional Pricing Details

Elasticsearch

General

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

Elasticsearch Editions & Modules

Edition
Standard$16.001
Gold$19.001
Platinum$22.001
EnterpriseContact Sales
  1. per month
Additional Pricing Details

Add comparison