tencent cloud

All product documents
TDSQL-C for MySQL
DocumentationTDSQL-C for MySQLFAQsBetween TDSQL-C for MySQL and TDSQL for MySQL
Between TDSQL-C for MySQL and TDSQL for MySQL
Download PDF
Last updated: 2023-11-09 15:34:55
Between TDSQL-C for MySQL and TDSQL for MySQL
Last updated: 2023-11-09 15:34:55
Download PDF
TDSQL-C for MySQL and TDSQL for MySQL are two different database products offered by Tencent Cloud. TDSQL-C for MySQL is designed based on cloud-native architecture, integrating the strengths of traditional databases, cloud computing, and cutting-edge hardware technologies. It supports a wide range of advanced features and capabilities to deliver highly elastic and reliable database services, which features high performance and PB-level storage. While TDSQL for MySQL is designed based on a source-replica architecture. It is a distributed database deployed on Tencent Cloud that supports automatic horizontal sharding and adopts a Shared Nothing architecture, where complete logical databases and tables are obtained and evenly distributed across multiple physical shard nodes in the backend. It provides a complete set of solutions for disaster recovery, backup, recovery, monitoring, and migration, making it suitable for scenarios with massive databases.

Detailed comparison

Comparison Item
TDSQL-C for MySQL
TDSQL for MySQL
Database type
A new-generation relational database that is born cloud-native
A distributed database that supports automatic horizontal sharding and adopts a Shared Nothing architecture
Architecture
Cluster: A cluster can contain only one read-write instance and up to 15 read-only instances.
InnoDB engine: Physical shard, with one shard containing 1 source and 1 replica or 1 source and 2 replicas
Engine
InnoDB
InnoDB
TDStore
Version
MySQL 5.7
MySQL 8.0
MySQL 8.0
Percona 5.7
MariaDB 10.1
Application scenarios
Businesses with great changes, frequent scaling, or needs of read-only instances to improve the read performance.
Game projects with frequent quick rollback required
Storage and access of petabytes of data
Scenarios requiring a high write QPS
Scenarios that are sensitive to source-replica delay
Ecommerce, finance, O2O, social applications, retail, SaaS service providers
Online business systems with a large data volume
Specification
Up to 88 cores and 710 GB memory p‌er instance
Up to 32 cores and 128 GB memory p‌er shard
Automatic backup
The default retention time is 7 days, and the maximum retention time can be set to 1830 days.
The default retention time is 7 days, and the maximum retention time can be set to 365 days.
Manual backup
Supported
Unsupported
Backup file format
Logical
Snapshot
Logical
Physical
Serverless
Supports serverless elastic expansion without manual intervention, and scales up or down automatically and quickly.
Unsupported
Maximum of creatable tables
There are no limits on the number of databases or tables that can be created. In theory, as long as there is enough space, more databases and tables can be created.
The maximum number of creatable tables is 5000 by default.
Read/write separation
Supported
Supported

‌Architecture comparison

TDSQL-C for MySQL

TDSQL for MySQL


Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback

Contact Us

Contact our sales team or business advisors to help your business.

Contact Us
Technical Support

Open a ticket if you're looking for further assistance. Our Ticket is 7x24 available.

Submit a Ticket
7x24 Phone Support
Hong Kong, China
+852 800 906 020 (Toll Free)
United States
+1 844 606 0804 (Toll Free)
United Kingdom
+44 808 196 4551 (Toll Free)
Canada
+1 888 605 7930 (Toll Free)
Australia
+61 1300 986 386 (Toll Free)
EdgeOne hotline
+852 300 80699
More local hotlines coming soon