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

Google Cloud Firestore vs InfluxDB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 7, 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

Google Cloud Firestore
Ranking in NoSQL Databases
15th
Average Rating
8.4
Reviews Sentiment
5.4
Number of Reviews
3
Ranking in other categories
Managed NoSQL Databases (11th)
InfluxDB
Ranking in NoSQL Databases
6th
Average Rating
8.0
Reviews Sentiment
6.5
Number of Reviews
20
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (7th), Network Monitoring Software (13th), IT Infrastructure Monitoring (14th)
 

Mindshare comparison

As of May 2026, in the NoSQL Databases category, the mindshare of Google Cloud Firestore is 3.0%, up from 0.9% compared to the previous year. The mindshare of InfluxDB is 5.2%, down from 9.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
InfluxDB5.2%
Google Cloud Firestore3.0%
Other91.8%
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.
Mugeesh Husain - PeerSpot reviewer
Team Lead, Software at Energybox
Time series data has been managed efficiently for IoT sensors but reporting still needs improvement
How InfluxDB can be improved is relevant since for Energy Box, we face certain issues. We have customers worldwide, including the United States, United Kingdom, and Europe, but when we expanded to China two years ago, they indicated that they do not support the cloud version there. Our application is built on the cloud, which required us to create a separate application for Azure China, which was painful for us. The second issue involves frequent version changes. For example, we started with version one, transitioned to version two, and I heard they are considering InfluxDB version three, reverting to earlier practices. InfluxDB should improve without completely changing its approach. Now we have to redo our work for InfluxDB version three. Regarding needed improvements, the documentation is sufficient, but pricing presents a challenge. InfluxDB has standard pricing, which is acceptable for large companies. However, for startups in our position, they should provide special discounts so everyone can utilize it. The pricing should adapt as companies grow, which is a reasonable expectation.

Quotes from Members

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

Pros

"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 the solution for maps, saving some locations, and chats."
"The most valuable features are Firestore's query capabilities and its real-time syncing functionality."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"The most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"InfluxDB reduced my time to show data without any interruption, also reducing the number of people needed to manage the project; it is very good to have InfluxDB in my project."
"The user interface is well-designed and easy to use. It provides a clear overview of the data, making it simple to understand the information at hand."
"The solution is very powerful."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"InfluxDB's best feature is that it's a cloud offering. Other good features include its time-series DB, fast time-bulk queries, and window operations."
"My advice for others looking into using InfluxDB is to use it the same way I did, because it is really stable, easy and friendly to use, and it is a great product overall."
 

Cons

"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."
"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."
"InfluxDB is generally stable, but we've encountered issues with the configuration file in our ticket stack. For instance, a mistake in one of the metrics out of a hundred KPIs can disrupt data collection for all KPIs. This happens because the agent stops working if there's an issue with any configuration part. To address this, it is essential to ensure that all configurations are part of the agent's EXE file when provided. This makes it easier to package the agent for server installation and ensures all KPIs are available from the server. Additionally, the agent cannot encrypt and decrypt passwords for authentication, which can be problematic when monitoring URLs or requiring authentication tokens. This requires additional scripting and can prolong service restart times."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"The error logging capability can be improved because the logs are not very informative."
"InfluxDB cannot be used for high-cardinality data. It's also difficult and time-consuming to write queries, and there are some issues with bulk API."
"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."
"I haven't seen a return on investment; unfortunately, I cannot share relevant metrics such as time saved, fewer employees needed, or money saved."
"In terms of features that I would like to see or have, in the community version, some features are not available. I would like to have clustering and authentication in the community version."
"However, I do wish the documentation and community resources around Flux were more extensive and beginner-friendly."
 

Pricing and Cost Advice

Information not available
"The tool is an open-source product."
"We are using the open-source version of InfluxDB."
"InfluxDB is open-source, but there are additional costs for scaling."
"InfluxDB recently increased its price. It is very expensive now."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
893,221 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
11%
University
11%
Government
9%
Healthcare Company
9%
Financial Services Firm
12%
Manufacturing Company
10%
Comms Service Provider
9%
Construction Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise4
Large Enterprise8
 

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 InfluxDB?
InfluxDB can be improved by addressing issues such as performance drops, queries being more difficult to understand, and its high memory usage. InfluxDB is not suitable for relational databases lik...
What is your primary use case for InfluxDB?
My main use case for InfluxDB is storing a time series database and analyzing data changes over time. I use InfluxDB to store my infrastructure and application metrics, logs, events, and data, and ...
What advice do you have for others considering InfluxDB?
I would advise others looking into using InfluxDB that if they want to store a time series database for monitoring, logging, and event-based tasks, and also want long-term retention of the database...
 

Also Known As

Firestore
No data available
 

Overview

 

Sample Customers

Information Not Available
ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
Find out what your peers are saying about Google Cloud Firestore vs. InfluxDB and other solutions. Updated: April 2026.
893,221 professionals have used our research since 2012.