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
100
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Vector Databases (6th)
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 August 2026, in the Search as a Service category, the mindshare of Elastic Search is 16.2%, down from 18.6% compared to the previous year. The mindshare of Solr is 5.2%, down from 6.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service Mindshare Distribution
ProductMindshare (%)
Elastic Search16.2%
Solr5.2%
Other78.6%
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

"What I like the most about Elastic Search is that I can store my data and search throughout my document."
"Elastic Search is very user-friendly, and we can easily integrate it with third-party models and other AWS S3 buckets."
"The AI-based attribute tagging is a valuable feature."
"ELK being an open source certainly provided a platform for our organization to get involved."
"The product is scalable with good performance."
"It gives us the possibility to store and query this data and also do this efficiently and securely and without delays."
"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."
"Elastic is doing a fantastic job by doing the indexing, and with a couple of indexing configurations, we are able to achieve our goal even though we are maintaining a huge amount of data per day, around millions of transactions for each record."
"It has improved our search ranking, relevancy, search performance, and user retention."
"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."
"This is an infinitely scalable product with state-of-the-art technology, and the value of Natural Language Search is tremendous."
"​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

"This product could be improved with additional security, and the addition of support for machine learning devices."
"I found an issue with Elasticsearch in terms of aggregation. They are good, yet the rules written for this are not really good."
"While Elastic Search is a good product, I see areas for improvement, particularly regarding the misconception that any amount of data can simply be dumped into Elastic Search."
"Enterprise scaling of what have been essentially separate, free open source software (FOSS) products has been a challenge, but the folks at Elastic have published new add-ons (X-Pack and ECE) to help large companies grow ELK to required scales."
"Its licensing needs to be improved. They don't offer a perpetual license. They want to know how many nodes you will be using, and they ask for an annual subscription. Otherwise, they don't give you permission to use it. Our customers are generally military or police departments or customers without connection to the internet. Therefore, this model is not suitable for us. This subscription-based model is not the best for OEM vendors. Another annoying thing about Elasticsearch is its roadmap. We are developing something, and then they say, "Okay. We have removed that feature in this release," and when we are adapting to that release, they say, "Okay. We have removed that one as well." We don't know what they will remove in the next version. They are not looking for backward compatibility from the customers' perspective. They just remove a feature and say, "Okay. We've removed this one." In terms of new features, it should have an ODBC driver so that you can search and integrate this product with existing BI tools and reporting tools. Currently, you need to go for third parties, such as CData, in order to achieve this. ODBC driver is the most important feature required. Its Community Edition does not have security features. For example, you cannot authenticate with a username and password. It should have security features. They might have put it in the latest release."
"Regarding what I dislike about Elastic Search, there is one issue that occurs because Elastic Search is not my primary database; it serves as a substitute database for the searching part."
"Apart from the good things, what I would like to see improved or enhanced in Elastic Search is the storage cost."
"It is hard to learn and understand because it is a very big platform. This is the main reason why we still have nothing in production. We have to learn some things before we get there."
"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."
"The solution's grammar and syntax should be easier."
"The performance for this solution, in terms of queries, could be improved."
"SolrCloud stability, indexing and commit speed, and real-time Indexing need improvement."
"Memory utilization could be better but it is an industrial strength tool so some overhead is to be expected."
"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."
 

Pricing and Cost Advice

"To access all the features available you require both the open source license and the production license."
"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."
"We are using the open-sourced version."
"we are using a licensed version of the product."
"The premium license is expensive."
"We use the free version for some logs, but not extensive use."
"The solution is affordable."
"We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
"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.
908,800 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Manufacturing Company
9%
Computer Software Company
8%
Outsourcing Company
7%
Outsourcing Company
13%
Comms Service Provider
11%
Construction Company
11%
Computer Software Company
10%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business40
Midsize Enterprise12
Large Enterprise50
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for ELK Elasticsearch?
The pricing for Elastic Search is mainly budgeted according to the organization budget, so we take it as a yearly subscription, and that is acceptable since we do get a fair discount when we are ta...
What needs improvement with ELK Elasticsearch?
When we get the logs, it is mostly about how we edit the configurations and how we make changes according to the requirements of our organization. In these cases, the logs sometimes can be a bit in...
What is your primary use case for ELK Elasticsearch?
I am the Elastic Search admin for my organization, and we are using Elastic Search to handle the traffic to GCP. The monitoring of all the clusters and all the deployments are quite good, and compa...
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: June 2026.
908,800 professionals have used our research since 2012.