Google Cloud Spanner vs. TencentDB

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.

Incentivized

• Super high availability
• Scales automatically
• High standard SLA

Incentivized

• 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.

Incentivized

At that point, we were looking at something [that] can hold our relational database, [...] provide stable connection, and maintain high ACID transition. BigTable is for nonrelational database so it was out of our [sight] very quickly. BigQuery is a data warehouse that can hold huge amount of data but not ideal for transition. AWS RDS is [...] similar to Spanner but because most of our services are already on GCP, so we went with Spanner.

Incentivized

• 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

Incentivized