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

Google Cloud Firestore 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

Google Cloud Firestore
Ranking in NoSQL Databases
15th
Ranking in Managed NoSQL Databases
11th
Average Rating
8.4
Reviews Sentiment
5.4
Number of Reviews
3
Ranking in other categories
No ranking in other categories
Redis
Ranking in NoSQL Databases
3rd
Ranking in Managed NoSQL Databases
5th
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
27
Ranking in other categories
In-Memory Data Store Services (1st), Vector Databases (3rd), AI Software Development (9th)
 

Mindshare comparison

As of August 2026, in the NoSQL Databases category, the mindshare of Google Cloud Firestore is 3.1%, up from 1.7% compared to the previous year. The mindshare of Redis is 8.3%, down from 9.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Redis8.3%
Google Cloud Firestore3.1%
Other88.6%
NoSQL Databases
 

Featured Reviews

PrathapSankar - PeerSpot reviewer
engagement Manager at Capgemini
Has simplified backend development for moderate user applications and supports efficient real-time data updates
A simplified way of building a logical layer on top of Firebase is necessary. Currently, the only option is to use cloud functions or Cloud Run functions. If they come up with an easier way of handling the logical layer between the frontend and backend, that would be beneficial. The UI of Firebase is much better compared to AWS or other Azure, but there is still scope for improving the usability of the UI. Additionally, some more AI features for automation can be added. The security layer can be enhanced, as currently, for data handling, there is just rule-based security; they can add one more layer of data security.
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 most valuable features are Firestore's query capabilities and its real-time syncing functionality."
"I use the solution for maps, saving some locations, and chats."
"One of the main features of Google Cloud Firestore's document management is the real-time listener; whenever there are any changes in the data, all the documents and applications that are reading through that particular document get automatically notified that there was some change, and automatically all the data gets refreshed."
"I use Redis mostly to cache repeated data that is required."
"What I like best about Redis is its fast and easy use. It has interesting algorithms like HyperLogLog and provides useful features. It's also good for implementing scalable rate limiting."
"The solution is fast, provides good performance, and is not too expensive."
"Redis is a simple service that does what it promises."
"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."
"Overall, my experience with Redis has been very positive, and it has played a key role in improving performance, scalability, and system responsiveness in our back-end system."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"Redis is a simple, powerful, and fast solution."
 

Cons

"Firestore needs improvements in its querying capabilities, particularly the ability to join tables and merge data from different tables before sending it to the front end."
"For lower volumes, it works fine, but once the volume increases, for use cases where the total number of users is less than 100,000 a month, Firebase is cheaper. But once you go beyond that, it becomes very expensive."
"I initially faced a problem creating groups in individual chats."
"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."
"It's actually quite expensive."
"For the PubSub feature, we had to create our own tools to monitor the events."
"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."
"The initial setup of Redis was difficult, with a rating of two or three out of ten."
"If we use a lot of data, it will eventually cost us a lot."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"There is a lack of documentation on the scalability of the solution."
 

Pricing and Cost Advice

Information not available
"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."
"Redis is not an overpriced solution."
"Redis is an open-source product."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
908,800 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
University
14%
Comms Service Provider
12%
Government
9%
Manufacturing Company
8%
Financial Services Firm
23%
Computer Software Company
9%
Comms Service Provider
6%
University
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 Google Cloud Firestore?
A simplified way of building a logical layer on top of Firebase is necessary. Currently, the only option is to use cloud functions or Cloud Run functions. If they come up with an easier way of hand...
What is your primary use case for Google Cloud Firestore?
Firebase is our main backend, so for managing authentications, for managing the backend database, and building cloud functions, it is all through Firebase. In the case of Google Cloud Firestore, th...
What advice do you have for others considering Google Cloud Firestore?
I have experience with Firebase, especially Firebase, then Google Cloud Computing Engine, and then Google Firebase Studio. Google Cloud Firestore is one of the offerings in Firebase, which is basic...
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

Firestore
Redis Enterprise
 

Overview

 

Sample Customers

Information Not Available
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 Google Cloud Firestore vs. Redis and other solutions. Updated: June 2026.
908,800 professionals have used our research since 2012.