To Span the data, then Spanner is the way
Use Cases and Deployment Scope
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.
Pros
- Scalability
- Sharding
- Interleaved Tables
- Cross Table Transactional Support
Cons
- Support for Views
- Support for more databases (schemas).
- More index types that can be supported (Functional)
- Backups (ie table/data backup) if data is deleted or truncate by accident.
Likelihood to Recommend
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.
