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
5th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
10
Ranking in other categories
Non-Relational Databases (3rd), Open Source Databases (12th), Network Monitoring Software (52nd), IT Infrastructure Monitoring (45th)
 

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.
PedroCampos - PeerSpot reviewer
A powerful, lightweight time series database with a simple query language and easy setup
Influx has TICK Stack, which contains multiple services and multiple products that work together. InfluxDB is just a time series database, and it works really well. I haven't yet had the time to look into the new stack based on Influx 2.0, but currently, as a time series database, InfluxDB is working the way it is supposed to work. 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. I would also like to have high availability features, such as replication, active-active, etc. If they can put an extra plugin or service on top of it, it would be something interesting. I am not sure if they have high availability to make it data center-aware for clustering. For example, I am not sure whether you can have it at different locations with big clusters that are location-aware. Even in their documentation or presentation, they talk too little about high availability and extended clusters with different locations. They might already have it in the newer versions. We have Influx 1.8 in our production in the stage and internal workloads environments. The other products in their ecosystem, such as Chronograf, can be improved. Chronograf is a dashboarding or visualization layer product, and that, for sure, can be improved.

Quotes from Members

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

Pros

"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 platform operates very quickly. It is easy to configure, connect, and query and integrates seamlessly with Grafana."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"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 from servers. It must be installed on Windows or Linux servers. During installation, ensure that the configuration file is correct to prevent issues. Once data is collected, it can be sent to InfluxDB. For visualization, you can use open-source tools like Grafana."
"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."
"The solution is very powerful."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"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 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."
 

Cons

"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."
"The solution doesn't have much of a user interface."
"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."
"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."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"The solution's UI can be more user-friendly."
"The error logging capability can be improved because the logs are not very informative."
"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."
"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."
 

Pricing and Cost Advice

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

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
14%
Computer Software Company
13%
Manufacturing Company
10%
Comms Service Provider
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?
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 coll...
What is your primary use case for InfluxDB?
I use the solution to store and manage data from various sensors in a production environment. I have developed a system where data from these sensors is communicated through an OPC UA receiver and ...
 

Comparisons

 

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 2025.
851,604 professionals have used our research since 2012.