Try our new research platform with insights from 80,000+ expert users

Elastic Search vs Redis comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

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 Vector Databases
2nd
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
67
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (9th), Search as a Service (1st)
Redis
Ranking in Vector Databases
4th
Average Rating
8.8
Reviews Sentiment
8.0
Number of Reviews
22
Ranking in other categories
NoSQL Databases (7th), In-Memory Data Store Services (1st)
 

Mindshare comparison

As of April 2025, in the Vector Databases category, the mindshare of Elastic Search is 5.8%, down from 7.1% compared to the previous year. The mindshare of Redis is 4.9%, down from 6.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases
 

Featured Reviews

Anand_Kumar - PeerSpot reviewer
Captures data from all other sources and becomes a MOM aka monitoring of monitors
Scalability and ROI are the areas they have to improve. Their license terms are based on the number of cores. If you increase the number of cores, it becomes very difficult to manage at a large scale. For example, if I have a $3 million project, I won't sell it because if we're dealing with a 10 TB or 50 TB system, there are a lot of systems and applications to monitor, and I have to make an MOM (Mean of Max) for everything. This is because of the cost impact. Also, when you have horizontal scaling, it's like a multi-story building with only one elevator. You have to run around, and it's not efficient. Even the smallest task becomes difficult. That's the problem with horizontal scaling. They need to improve this because if they increase the cores and adjust the licensing accordingly, it would make more sense.
Yaseer Arafat - PeerSpot reviewer
Unmatched Performance and Scalability for Modern Applications
Redis has room for improvement in a few areas. Enhanced tools for managing and monitoring clusters would be beneficial, as would built-in security mechanisms like advanced encryption and granular access controls. Simplifying setup and configuration could make Redis more accessible to new users. Introducing more enterprise-grade features, such as better multi-tenancy support and improved backup and restore capabilities, would also be advantageous. For the next release, it would be great to see enhanced cluster management tools, native multi-region supports for better data redundancy, integrated analytics for deeper insights, AI and ML integration features, and improved developer experience through enhanced SDKs and tools.

Quotes from Members

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

Pros

"It is stable."
"It is a stable and good platform."
"X-Pack provides good features, like authorization and alerts."
"The most valuable feature of Elastic Enterprise Search is the opportunity to search behind and between different logs."
"The AI-based attribute tagging is a valuable feature."
"The most valuable feature of the solution is its utility and usefulness."
"Elastic Enterprise Search is scalable. On a scale of one to 10, with one being not scalable and 10 being very scalable, I give Elastic Enterprise Search a 10."
"It's a stable solution and we have not had any issues."
"The ability to fetch and save data quickly is valuable."
"The in-memory data makes it fast."
"The most valuable features of Redis are its ease of use and speed. It does not have access to the disc and it is fast."
"I use Redis mostly to cache repeated data that is required."
"Redis is good for distributed caching management."
"The solution is fast, provides good performance, and is not too expensive."
"The solution's technical support team is good...The solution's initial setup process was straightforward."
"Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you use Redis efficiently."
 

Cons

"There is a lack of technical people to develop, implement and optimize equipment operation and web queries."
"Technical support should be faster."
"Elasticsearch could be improved in terms of scalability."
"Elasticsearch could improve by honoring Unix environmental variables and not relying only on those provided by Java (e.g. installing plugins over the Unix http proxy)."
"The real-time search functionality is not operational due to its impact on system resources."
"Elastic Search needs to improve authentication. It also needs to work on the Kibana visualization dashboard."
"There is another solution I'm testing which has a 500 record limit when you do a search on Elastic Enterprise Search. That's the only area in which I'm not sure whether it's a limitation on our end in terms of knowledge or a technical limitation from Elastic Enterprise Search. There is another solution we are looking at that rides on Elastic Enterprise Search. And the limit is for any sort of records that you're doing or data analysis you're trying to do, you can only extract 500 records at a time. I know the open-source nature has a lot of limitations, Otherwise, Elastic Enterprise Search is a fantastic solution and I'd recommend it to anyone."
"The price could be better. Kibana has some limitations in terms of the tablet to view event logs. I also have a high volume of data. On the initialization part, if you chose Kibana, you'll have some limitations. Kibana was primarily proposed as a log data reviewer to build applications to the viewer log data using Kibana. Then it became a virtualization tool, but it still has limitations from a developer's point of view."
"The initial setup of Redis was difficult, with a rating of two or three out of ten."
"In future releases, I would like Redis to provide its users with an option like schema validation. Currently, the solution lacks to offer such functionality."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"For the PubSub feature, we had to create our own tools to monitor the events."
"Redis could be improved by introducing a GUI to display key-value pair database information, as it is currently a CLI tool with no visual representation."
"The tool should improve by increasing its size limits and handling dynamic data better. We use the client ID or associate it with a key for static content. The solution will not be easy for a beginner. Unless you understand SQL data, it will be difficult to understand and use Redis. It also needs to be user-friendly."
"There is room for AWS to provide more options for server types or a way to configure more or less memory for them."
"There are some features from MongoDB that I would like to see included in Redis to enhance its overall efficiency, such as the ability to perform remote behaviour. MongoDB is more efficient in handling updates than deletions and is quicker in processing updates, but it can be slower regarding deletions. This can sometimes pose a challenge, especially when dealing with large datasets or frequent data manipulations that involve deletions. In such cases, I often rewrite columns or update values instead of directly deleting data, as it can be more efficient."
 

Pricing and Cost Advice

"The solution is affordable."
"Although the ELK Elasticsearch software is open-source, we buy the hardware."
"We are using the Community Edition because Elasticsearch's licensing model is not flexible or suitable for us. They ask for an annual subscription. We also got the development consultancy from Elasticsearch for 60 days or something like that, but they were just trying to do the same trick. That's why we didn't purchase it. We are just using the Community Edition."
"We use the free version for some logs, but not extensive use."
"Elastic Search is open-source, but you need to pay for support, which is expensive."
"This product is open-source and can be used free of charge."
"The tool is an open-source product."
"It can be expensive."
"Redis is not an overpriced solution."
"Redis is an open-source product."
"We saw an ROI. It made the processing of our transactions faster."
"The tool is open-source. There are no additional costs."
"Redis is an open-source solution. There are not any hidden fees."
report
Use our free recommendation engine to learn which Vector Databases solutions are best for your needs.
845,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
18%
Financial Services Firm
15%
Government
9%
Manufacturing Company
8%
Financial Services Firm
22%
Computer Software Company
15%
Educational Organization
7%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about ELK Elasticsearch?
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 anal...
What is your experience regarding pricing and costs for ELK Elasticsearch?
I don't know about pricing. That is dealt with by the sales team and our account team. I was not involved with that.
What needs improvement with ELK Elasticsearch?
I found an issue with Elasticsearch in terms of aggregation. They are good, yet the rules written for this are not really good. There is a maximum of 10,000 entries, so the limitation means that if...
What do you like most about Redis?
Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you u...
What needs improvement with Redis?
Redis could be improved by introducing a GUI to display key-value pair database information, as it is currently a CLI tool with no visual representation. Additionally, better documentation is neede...
What is your primary use case for Redis?
My primary use case for Redis has been leveraging it as a high-performance, in-memory data store to support real-time features in web applications. For instance, I used Redis to manage live chat sy...
 

Comparisons

 

Also Known As

Elastic Enterprise Search, Swiftype, Elastic Cloud
Redis Enterprise
 

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.
1. Twitter 2. GitHub 3. StackOverflow 4. Pinterest 5. Snapchat 6. Craigslist 7. Digg 8. Weibo 9. Airbnb 10. Uber 11. Slack 12. Trello 13. Shopify 14. Coursera 15. Medium 16. Twitch 17. Foursquare 18. Meetup 19. Kickstarter 20. Docker 21. Heroku 22. Bitbucket 23. Groupon 24. Flipboard 25. SoundCloud 26. BuzzFeed 27. Disqus 28. The New York Times 29. Walmart 30. Nike 31. Sony 32. Philips
Find out what your peers are saying about Elastic Search vs. Redis and other solutions. Updated: March 2025.
845,406 professionals have used our research since 2012.