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

Chroma vs Redis comparison

 

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

Chroma
Ranking in Vector Databases
11th
Average Rating
8.6
Reviews Sentiment
5.6
Number of Reviews
2
Ranking in other categories
No ranking in other categories
Redis
Ranking in Vector Databases
4th
Average Rating
8.8
Reviews Sentiment
5.9
Number of Reviews
26
Ranking in other categories
NoSQL Databases (4th), Managed NoSQL Databases (6th), In-Memory Data Store Services (1st), AI Software Development (13th)
 

Mindshare comparison

As of May 2026, in the Vector Databases category, the mindshare of Chroma is 7.1%, down from 13.0% compared to the previous year. The mindshare of Redis is 5.7%, up from 4.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases Mindshare Distribution
ProductMindshare (%)
Redis5.7%
Chroma7.1%
Other87.2%
Vector Databases
 

Featured Reviews

GagandeepSingh1 - PeerSpot reviewer
Data Science Manager at Zykrr
A simple and easy to use solution that can run on a two-course CPU
We collect customer's feedback, and then we present it to the clients It's very easy to set up and runs easily. It doesn't require great hardware and can run on a two-course CPU with four gigs. The hybrid algorithm needs improvement. I have been using Chroma for one year.  I had some trouble…
Varuns Ug - PeerSpot reviewer
Senior software developer at Makemytrip
Caching has accelerated complex workflows and delivers low latency for high-traffic microservices
A few features of Redis that I use on a day-to-day basis and feel are among the best are extremely low latency and high throughput. Since Redis is in-memory, it makes it ideal for cases such as caching and rate limiting where response time is critical. TTL expiry support is very useful in Redis as it allows me to automatically evict stale data without manual cleanup, which is something I use heavily in my caching strategy. Another point I can mention is that the rich data structures such as strings, hashes, and even sorted sets are very powerful. I have used strings for caching responses and counters, whereas I have used hashes for storing structured objects. One more feature I can tell you about is atomic operations. Redis guarantees atomicity for operations such as incrementing a counter, which is very useful for rate limiting and avoiding race conditions in distributed systems. Finally, I want to emphasize that Redis is easy to scale and integrate, whether through clustering or using a distributed cache across microservices. Redis has impacted my organization positively by providing default support that is very useful. For metrics, in one of my core systems, introducing Redis as a distributed cache helped me achieve around an 80% cache hit rate, which reduced repeated downstream services. Real API latency also improved from around two seconds to approximately 450 milliseconds for P99. It also helped reduce the load on dependent services and databases, which improved overall system reliability.

Quotes from Members

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

Pros

"It's very easy to set up and runs easily."
"The solution's most valuable feature is its documentation, which allows new users to easily learn, deploy, and use it."
"Redis acts as an in-memory search tool that improves the speed of operations, allowing for quicker data retrieval and enhancing the performance of applications."
"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."
"Redis has multiple valuable features such as being a free and reliable open-source tool."
"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 a simple, powerful, and fast solution."
"I find Redis valuable primarily for its caching capabilities, particularly in handling cache requests effectively. Its simplicity in managing key-value pairs for caching is one of its strengths, making it a preferred choice over more complex databases like MongoDB for specific use cases. However, I haven't explored Redis extensively for managing complex data structures beyond caching, as MongoDB might be more suitable for such scenarios."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
 

Cons

"I think Chroma doesn't have a ready-made containerized image available."
"The hybrid algorithm needs improvement."
"There is a lack of documentation on the scalability of the solution."
"Redis should have an option to operate without Docker on a local PC."
"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."
"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."
"For the PubSub feature, we had to create our own tools to monitor the events."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"One limitation is that Redis is memory-based, so scaling can become expensive compared to disk-based systems."
 

Pricing and Cost Advice

"The current version is an open-source."
"The tool is open-source. There are no additional costs."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is an open-source product."
"Redis is not an overpriced solution."
"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.
893,221 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Computer Software Company
10%
Manufacturing Company
9%
Government
8%
Financial Services Firm
24%
Computer Software Company
10%
Comms Service Provider
7%
University
6%
 

Company Size

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

Questions from the Community

What do you like most about Chroma?
The solution's most valuable feature is its documentation, which allows new users to easily learn, deploy, and use it.
What needs improvement with Chroma?
The hybrid algorithm needs improvement.
What is your primary use case for Chroma?
We collect customer's feedback, and then we present it to the clients.
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?
Overall, Redis is a powerful and reliable tool, but there are a few areas for improvement. One limitation is that Redis is memory-based, so scaling can become expensive compared to disk-based syste...
What is your primary use case for Redis?
My main use case for Redis is caching frequently accessed data to improve performance and reduce database load. For example, I cache API responses and user-related data so that repeated requests ca...
 

Comparisons

 

Also Known As

No data available
Redis Enterprise
 

Overview

 

Sample Customers

1. Google 2. Netflix 3. Amazon 4. Facebook 5. Microsoft 6. Apple 7. Twitter 8. Spotify 9. Adobe 10. Uber 11. Airbnb 12. LinkedIn 13. Pinterest 14. Snapchat 15. Dropbox 16. Salesforce 17. IBM 18. Intel 19. Oracle 20. Cisco 21. HP 22. Dell 23. Samsung 24. Sony 25. LG 26. Panasonic 27. Philips 28. Toshiba 29. Nokia 30. Motorola 31. Xiaomi 32. Huawei
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 Chroma vs. Redis and other solutions. Updated: April 2026.
893,221 professionals have used our research since 2012.