To Span the data, then Spanner is the way
Overall Satisfaction with Google Cloud Spanner
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.
- Backups specifically if transactional data is deleted. Restoring made us lose time.
- Sharding on Horizontal level was quick and easy. Deployment and increasing nodes is easy
- Large dataset handling.
- ACID compliance
Spanner scales quickly compared to Amazon RDS. Azure Database is about the same as well. MongoDB can scale to horizontal scalability, however, because Mongo doesn't support full ACID, Spanner comes into that aspect. GCP Cloud SQL not as scalable as Spanner. Spanner has more functionality than MongoDB and Amazon RDS & Azure Databases.
Do you think Google Cloud Spanner delivers good value for the price?
No
Are you happy with Google Cloud Spanner's feature set?
Yes
Did Google Cloud Spanner live up to sales and marketing promises?
Yes
Did implementation of Google Cloud Spanner go as expected?
Yes
Would you buy Google Cloud Spanner again?
Yes
Comments
Please log in to join the conversation