What is our primary use case?
We use it for managing workflows, workflow data, and state management. We'll use it for tenant metadata information and keeping it.
We have some BI use cases as well. We are in the automation industry, so, in general, whatever is required for automation, we keep all that information.
What is most valuable?
We are using standard SQLs features only, so we don't use any very specific feature assets.
One feature we've found pretty interesting was their support, which is multi-region support. They have good multi-region failure support, and we can just set up there and read replicas directly and we can fall back. We are quite pleased with the results.
The initial setup is straightforward.
It's stable.
The solution can scale.
What needs improvement?
The purging of the data could be better. We don't have a good mechanism to deal with the old data, especially when the data grows. We see latency issues, so we were forced to introduce an in-memory store. Otherwise, the solution is fine.
The enterprise edition is quite expensive.
For how long have I used the solution?
I've used the solution for a few months.
Buyer's Guide
Google Cloud SQL
November 2024
Learn what your peers think about Google Cloud SQL. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,660 professionals have used our research since 2012.
What do I think about the stability of the solution?
The stability is good. There are no bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
Currently, our DevOps team is using the product, and we have 20 to 30 people using it. We have plans to increase usage.
While it is scalable, I don't yet have practical experience with the process.
How was the initial setup?
The solution is very easy to set up. It's not overly complex.
The deployment is very fast. It was only a few minutes.
I'd rate the solution three and a half out of five in terms of ease of setup.
I'd rate it higher if there was general serverless support or good best practices by way of documentation for setting everything up. We are using the enterprise model. Having best practices and serverless support would make it a bit better.
Right now, we don't need much maintenance as we're still in the beginning stages and don't have much production workload.
What about the implementation team?
We were able to handle the setup ourselves. The documentation was good enough to follow so that the setup was easy.
What's my experience with pricing, setup cost, and licensing?
The pricing is interesting. For the enterprise edition, it was almost three times the cost of the standard edition. There should be some more clarity on that. It was not very clear why it's so much more or what the differences are. It requires better documentation.
What other advice do I have?
We're a customer and end-user.
We moved quite recently in production. In terms of the development run, we were on AWS. Now, some of the workloads we are moving to GCP even though we have been an Amazon shop for a long time.
We are working on the latest version of the solution.
I'd rate the solution eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Google
Disclosure: I am a real user, and this review is based on my own experience and opinions.