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

Neo4j Graph Database vs Redis comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 15, 2026

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

Neo4j Graph Database
Ranking in NoSQL Databases
12th
Average Rating
8.6
Reviews Sentiment
7.7
Number of Reviews
6
Ranking in other categories
No ranking in other categories
Redis
Ranking in NoSQL Databases
4th
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
26
Ranking in other categories
Managed NoSQL Databases (5th), In-Memory Data Store Services (1st), Vector Databases (5th), AI Software Development (9th)
 

Mindshare comparison

As of November 2026, in the NoSQL Databases category, the mindshare of Neo4j Graph Database is 6.3%, up from 5.9% compared to the previous year. The mindshare of Redis is 7.8%, down from 8.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Redis7.8%
Neo4j Graph Database6.3%
Other85.9%
NoSQL Databases
 

Featured Reviews

RT
VP odfTechnology at Enterpi Software Solutions Private Limited
Delivers superior search and data aggregation capabilities
Neo4j helps with advanced search needs, providing good search results and aggregates compared to MongoDB. Aggregating with MongoDB can be difficult; however, with Neo4j, it's easier. Aggregating data, backing up, and creating new clusters are user-friendly from the back end. In DevOps web deployment, we noticed no database issues. We created Docker instances and set them up efficiently, managing databases up to 50 gigabytes.
RituRaj - PeerSpot reviewer
SDE 2 at Virtusa
Caching has improved response times and reduces database load for high-traffic applications
Redis is very reliable, but it could be improved in areas such as monitoring, debugging, and feasibility into memory use. Better built-in tools for observability would help teams manage it more effectively at scale. Managing memory efficiently and troubleshooting issues can sometimes require additional tooling, so these areas can also be improved.One practical challenge I experienced is managing memory efficiently. Since Redis is in-memory, we need to carefully configure eviction policies and monitor usage. Debugging cache-related issues such as stale data or cache invalidation can sometimes be tricky. Additionally, tuning memory usage and eviction policies needs to be planned very carefully.

Quotes from Members

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

Pros

"The graph modeling paradigm suits our data set well, where there may be orders of magnitude more connections between data points than data points themselves."
"Enables people to understand what the business problem is and how the technology helps."
"It is good for search-based tasks, providing solid search results and aggregate results."
"For now, the tool doesn't break down or stop, so it is quite stable."
"The solution's best feature is how it differs from traditional SQL databases. It's hard to map people and find those near me in SQL, which requires long, complex queries. Neo4j Graph Database makes this easier with simpler queries. It also supports more data types, like JSON, which SQL doesn't."
"As a graph database, I am surprised at their performance and response time."
"It enables circumstances which would have been a complex problem to be simplified."
"Neo4j helps with advanced search needs, providing good search results and aggregates compared to MongoDB."
"Redis has had a positive impact by improving application performance, reducing database load, and making the system more scalable."
"Redis has multiple valuable features such as being a free and reliable open-source tool."
"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."
"Redis is a powerful and reliable tool for improving application performance."
"The solution is fast, provides good performance, and is not too expensive."
"Redis is a simple service that does what it promises."
"The online interface is very fast and easy to use."
"The best thing about Redis is its ability to handle large amounts of data without frequently hitting the database. You can store data in temporary memory, especially for high-volume data."
 

Cons

"For me, when the tool was deployed on an on-premises model, it was a little bit difficult the first time."
"So far, we have not had any issues and are happy with the product in general."
"There are things I found unintuitive or difficult to understand, however I can't say this is a deficiency in the product and likely more a function of my relatively low experience."
"There are concerns about performance and whether the tool can necessarily scale to provide the solution."
"The only problem is that the community is quite small."
"The tool could improve by having more resources, especially for Golang, which we use. It lacks good basic libraries and doesn't have an ORM (Object-Relational Mapping) tool, which many NoSQL databases have. We thought about building an ORM for the Neo4j Graph Database but are too busy."
"The only thing is the lack of a GUI application. There was a time when we needed to resolve an issue in production. If we had a GUI, it would have been easier."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"The initial setup of Redis was difficult, with a rating of two or three out of ten."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"It's actually quite expensive."
"The solution's pricing for a local installation is very expensive."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"There is room for AWS to provide more options for server types or a way to configure more or less memory for them."
 

Pricing and Cost Advice

"The solution is open source so that you can use it for free. They also offer an enterprise version with its billing. If your company is earning well, I suggest using the enterprise version. Otherwise, you can deploy it on your own cloud and pay based on usage."
"The tool is not expensive."
"Redis is not an overpriced solution."
"Redis is an open-source solution. There are not any hidden fees."
"Redis is an open-source product."
"The tool is open-source. There are no additional costs."
"We saw an ROI. It made the processing of our transactions faster."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
920,769 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Construction Company
10%
Comms Service Provider
8%
University
7%
Financial Services Firm
21%
Comms Service Provider
8%
Computer Software Company
7%
Outsourcing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise6
Large Enterprise10
 

Questions from the Community

What needs improvement with Neo4j Graph Database?
The only problem is that the community is quite small.
What is your primary use case for Neo4j Graph Database?
We have used Neo4j in microservices. In one of the microservices, we used Neo4j since we have some requirements similar to MongoDB plus Elasticsearch. It performs both functions. Instead of doing t...
What advice do you have for others considering Neo4j?
We have used both editions without any difficulty. In the fourth year, they provided the software, and we installed three additional community editions with no issues. Backing up required some effo...
What needs improvement with Redis?
Making management easier, especially for teams operating large Redis clusters, would be helpful. More advanced built-in observability, performance insights, and automated recommendations would help...
What is your primary use case for Redis?
Redis is used primarily as a caching layer to provide a high-performance caching solution that improves application response times and reduces load on backend services and databases. We use it main...
What advice do you have for others considering Redis?
There are a couple of things to consider when using Redis. It is a supporting layer, not a main database. Identifying specific use cases where Redis can provide the most value, such as caching, ses...
 

Also Known As

No data available
Redis Enterprise
 

Overview

 

Sample Customers

Walmart, Telenor, Wazoku, Adidas, Cerved, GameSys, eBay, Schleich, ICIJ, die Bayerisch, Megree, InfoJobs, LinkedIn
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 Neo4j Graph Database vs. Redis and other solutions. Updated: September 2026.
920,769 professionals have used our research since 2012.