No more typing reviews! Try our Samantha, our new voice AI agent.

Elastic Search vs Solr comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Elastic Search
Ranking in Search as a Service
1st
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
96
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Vector Databases (2nd)
Solr
Ranking in Search as a Service
10th
Average Rating
7.8
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2026, in the Search as a Service category, the mindshare of Elastic Search is 17.6%, up from 15.6% compared to the previous year. The mindshare of Solr is 5.1%, down from 6.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service Mindshare Distribution
ProductMindshare (%)
Elastic Search17.6%
Solr5.1%
Other77.3%
Search as a Service
 

Featured Reviews

reviewer2817942 - PeerSpot reviewer
Senior Software Engineer at a consultancy with 11-50 employees
Logging and vector search have transformed observability and empowered reliable ai agents
Elastic Search is not specifically being used for certain purposes. I deploy Elastic Search database on the cloud and use cloud services so that nobody can attack. However, I do not use Elastic Search to resolve attack issues. The basic main purpose of Elastic Search, as of now, I feel it can do more in the AI area. Sometime I saw that when I am developing RAG and have to generate the embeddings, which I call metadata, sometimes it tries to fail. That durability or issue handling should be improved, but apart from that, I did not find anything as of now. As per my use case, whatever I am using seems pretty good. Apart from that, some definitely improvement will be there. One improvement is that it should be faster. Whenever I am searching any logs, it takes much time. For example, if I open my log in Notepad or a similar tool, I can search the text within a second. With Elastic Search, it takes a little bit of time, ten to fifteen seconds. That can be improved. Sometimes, engineers take time to assign when I create a ticket.
it_user823641 - PeerSpot reviewer
Senior Search Engineer at a financial services firm with 51-200 employees
The Natural Language Search capability is helpful and intuitive for our users
The initial setup is complex because this is a distributed system, and you have to make sure that every individual node is aware of every other node in existence. This search engine has a large capacity, so you need to make sure that there is enough buffer space. We took one month to deploy and perform a fresh setup. Our strategy was to start with a local data center, before venturing into cross data center replicas. A staff size of two to four people is suitable for deploying and maintaining the solution, depending upon the scale. They would set up the solution and put monitoring in place for the indexing jobs, as well as design the schema so that the data can feed well.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The observability is the best available because it provides granular insights that identify reasons for defects."
"Logsign provides us with the capability to execute multiple queries according to our requirements. The indexing is very high, making it effective for storing and retrieving logs. The real-time analytics with Elastic benefits us due to the huge traffic volume in our organization, which reaches up to 60,000 requests per second. With logs of approximately 25 GB per day, manually analyzing traffic behavior, payloads, headers, user agents, and other details is impractical."
"Aggregation is faster than querying directly from a database, like Postgres or Vertica, and it's much faster if I want to do aggregation, which allows me to store logs and find anomalies effectively."
"This product has notably improved the way we store and use logs, from having a more user-friendly, centralized solution (for those who just needed a quick glance, without being masters of sed and awk) to implementing various mechanisms for machine-learning from our logs, and sending alerts for anomalies."
"The solution is valuable for log analytics."
"Elastic Enterprise Search is a very good solution and they should keep doing good work."
"I appreciate that Elastic Enterprise Search is easy to use and that we have people on our team who are able to manage it effectively."
"The flexibility and the support for diverse languages that it provides for searching the database are most valuable, and we can use different languages to query the database."
"The most valuable feature is the ability to perform a natural language search."
"We use Solr to index over 600k documents; it's very fast, flexible to use, and the speed of indexing individual documents has been great."
"It has improved our search ranking, relevancy, search performance, and user retention."
"This is an infinitely scalable product with state-of-the-art technology, and the value of Natural Language Search is tremendous."
"It has improved our search ranking, relevancy, search performance, and user retention."
"One of the best aspects of the solution is the indexing. It's already indexed to all the fields in the category. We don't need to spend so much extra effort to do the indexing. It's great."
"​Sharding data, Faceting, Hit Highlighting, parent-child Block Join and Grouping, and multi-mode platform are all valuable features."
"One of the best aspects of the solution is the indexing; it's already indexed to all the fields in the category, so we don't need to spend so much extra effort to do the indexing, which is great."
 

Cons

"Machine learning on search needs improvement."
"I would like to see more integration for the solution with different platforms."
"The reports could improve."
"Elastic Enterprise Search could improve the report templates."
"It should be easier to use. It has been getting better because many functions are pre-defined, but it still needs improvement."
"The most significant issue I find with Elastic Search is that it gets out of sync, and this has happened in both cases where I have implemented it."
"There are a few things that did not work for us. When doing a search in a bigger setup, with a huge amount of data where there are several things coming in, it has to be on top of the index that we search."
"Elastic Enterprise Search could improve the report templates."
"The performance for this solution, in terms of queries, could be improved."
"The performance for this solution, in terms of queries, could be improved."
"The solution's grammar and syntax should be easier."
"SolrCloud stability, indexing and commit speed, and real-time Indexing need improvement."
"Encountered issues with both master-slave and SolrCloud. Indexing and serving traffic from same collection has very poor performance; some components are slow for searching."
"With increased sharding, performance degrades. Merger, when present, is a bottle-neck. Peer-to-peer sync has issues in SolrCloud when index is incrementally updated."
"Memory utilization could be better but it is an industrial strength tool so some overhead is to be expected."
"It does take a little bit of effort to use and understand the solution. It would help us a lot if the solution offered up more documentation or tutorials to help with training or troubleshooting."
 

Pricing and Cost Advice

"This is a free, open source software (FOSS) tool, which means no cost on the front-end. There are no free lunches in this world though. Technical skill to implement and support are costly on the back-end with ELK, whether you train/hire internally or go for premium services from Elastic."
"The price of Elastic Enterprise is very, very competitive."
"The solution is affordable."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"The version of Elastic Enterprise Search I am using is open source which is free. The pricing model should improve for the enterprise version because it is very expensive."
"The solution is not expensive because users have the option of choosing the managed or the subscription model."
"To access all the features available you require both the open source license and the production license."
"​The pricing and license model are clear: node-based model."
"The only costs in addition to the standard licensing fees are related to the hardware, depending on whether it is cloud-based, or on-premise."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
893,221 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Computer Software Company
9%
Manufacturing Company
9%
Retailer
6%
Computer Software Company
12%
Comms Service Provider
9%
Manufacturing Company
9%
Outsourcing Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business39
Midsize Enterprise12
Large Enterprise47
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for ELK Elasticsearch?
When it comes to pricing, I think we had to pay AWS approximately 1,000 to 1,200 per month for the overall stack. I am not quite certain about how much Elastic Search costs specifically because I w...
What needs improvement with ELK Elasticsearch?
Elastic Search has many features, including Kibana and Logstash, which we regularly use. However, one downside in our product is cost, as it can be expensive when maintaining multiple shards and in...
What is your primary use case for ELK Elasticsearch?
As a developer, I use Elastic Search in developing one of my applications, basically integrating the back-end with Elastic Search. Our main use case for Elastic Search is for Logstash, which is a s...
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

Elastic Enterprise Search, Swiftype, Elastic Cloud
No data available
 

Overview

 

Sample Customers

T-Mobile, Adobe, Booking.com, BMW, Telegraph Media Group, Cisco, Karbon, Deezer, NORBr, Labelbox, Fingerprint, Relativity, NHS Hospital, Met Office, Proximus, Go1, Mentat, Bluestone Analytics, Humanz, Hutch, Auchan, Sitecore, Linklaters, Socren, Infotrack, Pfizer, Engadget, Airbus, Grab, Vimeo, Ticketmaster, Asana, Twilio, Blizzard, Comcast, RWE and many others.
eHarmony, Sears, StubHub, Best Buy, Instagram, Netflix, Disney, AT&T, eBay, AOL, Bloomberg, Comcast, Ticketmaster, Travelocity, MTV Networks
Find out what your peers are saying about Elastic Search vs. Solr and other solutions. Updated: April 2026.
893,221 professionals have used our research since 2012.