Google Cloud Spanner Reviews & Insights

Google Spanner is being used as a relational database in comparison to Amazon RDS. The issues we're having with Amazon RDS is scalability horizontally. We need a db for transactional use which is leaning towards the OLTP end. Amazon RDS helps us to a certain extent. Google Cloud Spanner was tested out for scalability, since we hit limits with Amazon RDS. The usage is used by the company product used internally and with consumers.

Google Cloud Spanner is suited for limitless horizontal scaling while maintaining strong consistency which needs to support ACID. NoSQL databases work in scaling but no ACID support. RDBMS support ACID, but horizontal scaling is not as great. The API it provides result in some limitations to related areas of the code, such as connection pools or database linking framework. So high # of connection pools can vary.

As our business grows rapidly, we need a database that can enable us to have [the] capacity in scaling and availability and it also needs to be [a] relational database. At that time we are already a Google Cloud Platform customer and after some researches, we think Google Cloud Spanner can give us both.

If you have a large relational database and it is growing fast on daily basis, and if you have a strong need in ACID across all your clusters, and most importantly, if you need to maintain high availability in a large region, Google Cloud Spanner can be a very good choice.