Google Cloud SQL vs. InfluxDB

Although Google Cloud SQL has room for improvement by addressing a minor lack of features, its features and services keep it high among other SQL database products. It is very fast compared to others. Since it is cloud-based, maintenance is also easier. Integration capabilities are also more than expected.

Incentivized

InfluxDB is very good at storing monitoring metrics (e.g. performance data). InfluxDB is not the right choice if you need to store other data types (like plain text, data relations etc.).

Incentivized

• Very easy to use and migrate existing database systems to Google Cloud SQL system
• Easy to query with real-time query assessment as well as processing metrics to help optimize the queries
• No need to learn any other querying language (like in Hadoop ecosystem), as SQL works pretty fine
• Easy-to-use GCP portal to type in queries and see the results on the screen (no need to go on command line )
• Easy to set up

Incentivized

• Perfect handling telemetry data.
• Low latency, near real time.
• SQL-like language makes it easier to query.

Incentivized

• Increasing support for more database engines may enable a wider range of application needs to be met.
• Implementing and updating cutting-edge security features on a constant basis.
• Streamlining and enhancing the tools for transferring data to Google Cloud SQL from on-premises databases or other cloud providers.

• GUI based administrator console

Incentivized

InfluxDB is a near perfect product for time series database engines. The relatively small list of cons are heavily outweighed by it's ability to just work and be a very flexible and powerful database engine. The community and support provided by the corporation are the only areas I have little experience.

Incentivized

Basically on personal experience. Google Cloud SQL is an excellent database for a large number of varied use cases. Often the only necessary change is a single line change in a config file and setup some accesses. It is fast enough almost all the time and a breeze to set up. Lack of stored procedures and in TDE encryption is the only reason which it not a 10/10

Incentivized

GCP support in general requires a support agreement. For small organizations like us, this is not affordable or reasonable. It would help if Google had a support mechanism for smaller organizations. It was a steep learning curve for us because this was our first entry into the cloud database world. Better documentation also would have helped.

Incentivized

We have worked with the InfluxDB support team a few times so far and it has been positive. Issues submitted are worked on promptly and we have good feedback.

Incentivized

Google SQL was great as a first SQL provision. It quickly enabled the apps to be built and scaled as needed for a while. It was robust and adaptable as needed and easy to export as needed when ready, depending on growth. Cost-wise, it's a good choice and requires little investment to get going.

Incentivized

To be honest, I didn't look at alternatives since InfluxDB performs very well if you can oversee the lack of security and HA features. But for all challenges, there is an easy solution which brings you forward (e.g. read load balancing can be achieved by using a common HTTPS load balancer).

Incentivized

• When first migrated to a cloud environment, the Cloud SQL instance had a higher cost than our former MySQL VM instance, but many other infrastructure costs had also been reduced and the total balance of our migration to the cloud was a reduction of 45% of our infrastructure costs.
• DB performance has increased and maintenance tasks reduced in a high percentage.
• Disaster recovery plans are easier to follow now than before our cloud migration.

Incentivized

• Provided us a time series DB.
• With the SQL-like language, it is very easy to learn.
• Empowered us to keep track of our events.

Incentivized