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

Elastic Search vs Solr comparison

Why PeerSpot?
 

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 (8th), Vector Databases (6th)
Solr
Ranking in Search as a Service
9th
Average Rating
7.8
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2026, in the Search as a Service category, the mindshare of Elastic Search is 15.3%, down from 18.9% compared to the previous year. The mindshare of Solr is 6.5%, up from 5.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service Mindshare Distribution
ProductMindshare (%)
Elastic Search15.3%
Solr6.5%
Other78.2%
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

"X-Pack provides good features, like authorization and alerts."
"The most valuable feature of Elasticsearch is its convenience in handling unstructured data."
"The most valuable feature is the out of the box Kibana."
"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."
"There's lots of processing power. You can actually just add machines to get more performance if you need to. It's pretty flexible and very easy to add another log. It's not like 'oh, no, it's going to be so much extra data'. That's not a problem for the machine. It can handle it."
"A good use case is saving metadata of your systems for data cataloging. Various systems, like those opened in metadata and similar applications, use Elasticsearch to store their text data."
"Elastic Search is very user-friendly, and we can easily integrate it with third-party models and other AWS S3 buckets."
"This is a very rich product, and it's got a very wide functionality, and a wide range of functionalities which I don't see in the other products, especially not in the cheaper ones."
"This is an infinitely scalable product with state-of-the-art technology, and the value of Natural Language Search is tremendous."
"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."
"​Sharding data, Faceting, Hit Highlighting, parent-child Block Join and Grouping, and multi-mode platform are all valuable features."
"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, so we don't need to spend so much extra effort to do the indexing, which is great."
 

Cons

"The solution must provide AI integrations."
"The setup is somewhat complicated due to multiple dependencies and relations with different systems."
"This product could be improved with additional security, and the addition of support for machine learning devices."
"Could have more open source tools and testing."
"I would rate the stability a seven out of ten. We faced a few issues."
"It was not possible to use authentication three years back. You needed to buy the product's services for authentication."
"We have an issue with the volume of data that we can handle."
"New Relic could be more flexible, similar to Elasticsearch."
"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."
"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."
"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."
"The solution's grammar and syntax should be easier."
"The performance for this solution, in terms of queries, could be improved."
"Memory utilization could be better but it is an industrial strength tool so some overhead is to be expected."
 

Pricing and Cost Advice

"An X-Pack license is more affordable than Splunk."
"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."
"ELK has been considered as an alternative to Splunk to reduce licensing costs."
"​The pricing and license model are clear: node-based model."
"The solution is not expensive because users have the option of choosing the managed or the subscription model."
"Elastic Search is open-source, but you need to pay for support, which is expensive."
"We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
"The solution is free."
"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.
920,769 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Manufacturing Company
9%
Outsourcing Company
9%
Comms Service Provider
7%
Comms Service Provider
16%
Financial Services Firm
14%
Outsourcing Company
14%
Construction Company
12%
 

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: September 2026.
920,769 professionals have used our research since 2012.