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

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
13th
Average Rating
8.6
Reviews Sentiment
8.1
Number of Reviews
2
Ranking in other categories
Managed NoSQL Databases (10th)
InfluxDB
Ranking in NoSQL Databases
4th
Average Rating
8.2
Reviews Sentiment
6.6
Number of Reviews
11
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (9th), Network Monitoring Software (22nd), IT Infrastructure Monitoring (26th)
 

Mindshare comparison

As of August 2025, in the NoSQL Databases category, the mindshare of Google Cloud Firestore is 1.7%, up from 0.0% compared to the previous year. The mindshare of InfluxDB is 7.6%, down from 12.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases
 

Featured Reviews

AnthonyAbah - PeerSpot reviewer
Real-time syncing boosts productivity with efficient data management
The most valuable features are Firestore's query capabilities and its real-time syncing functionality. The queries are efficient, apart from some limitations. Real-time syncing allows any changes at the backend to automatically appear at the frontend. This is highly useful as it eliminates the need to reload the browser to see the updates.
DeepakR - PeerSpot reviewer
An open-source database that can be used to insert data
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.

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."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"While I would rate InfluxDB a ten on a scale of one to ten, users should be thoughtful about matching the engine to their specific needs."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"In our case, it started with a necessity to fill the gap that we had in monitoring. We had very reactive monitoring without trend analysis and without some advanced features. We were able to implement them by using a time series database. We are able to have all the data from applications, logs, and systems, and we can use a simple query language to correlate all the data and make things happen, especially with monitoring. We could more proactively monitor our systems and our players' trends."
"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."
"The platform operates very quickly. It is easy to configure, connect, and query and integrates seamlessly with Grafana."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
 

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."
"I initially faced a problem creating groups in individual chats."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"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."
"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."
"The solution's UI can be more user-friendly."
"InfluxDB can improve by including new metrics on other technologies. They had some changes recently to pool data from endpoints but the functionality is not good enough in the industry."
"The solution doesn't have much of a user interface."
"The error logging capability can be improved because the logs are not very informative."
 

Pricing and Cost Advice

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

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
12%
Computer Software Company
11%
Comms Service Provider
8%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What needs improvement with Google Cloud Firestore?
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. The pricing model is also...
What is your primary use case for Google Cloud Firestore?
I use Google Cloud Firestore for user management and data storage, primarily for web applications. Firestore helps sync data between different users and stores documents efficiently.
What advice do you have for others considering Google Cloud Firestore?
I highly recommend Google Cloud Firestore due to its cost-effectiveness and real-time syncing capabilities. However, it needs improvements in querying functionalities and a simplified pricing model.
What do you like most about InfluxDB?
InfluxDB is a database where you can insert data. However, it would be best if you had different components for alerting, data sending, and visualization. You need to install tools to collect data ...
What needs improvement with InfluxDB?
It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster. Replicating data for on-prem development and testing is difficult. Having a SQL abstrac...
What is your primary use case for InfluxDB?
InfluxDB is the main component in our large enterprise-scale streaming data application for maritime vessels. We collect position data from vessels around the coast once per second, put it on a Kaf...
 

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: July 2025.
865,384 professionals have used our research since 2012.