Users can create a production-level MySQL database with simple clicks in the console, which is ready to use out of the box, and fine configuration and tuning features are provided.
Users can create a production-level MySQL database with simple clicks in the console, which is ready to use out of the box, and fine configuration and tuning features are provided.
With leading I/O throughput and a deeply customized and developed MySQL kernel, the performance of TencentDB for MySQL far exceeds self-built databases. It has a simplified backend architecture, which is easier to maintain and manage.
With leading I/O throughput and a deeply customized and developed MySQL kernel, the performance of TencentDB for MySQL far exceeds self-built databases. It has a simplified backend architecture, which is easier to maintain and manage.
TencentDB for MySQL provides 99.9999999% data reliability and up to 99.99% service availability, with complete automatic data backup and lossless recovery mechanisms.
TencentDB for MySQL provides 99.9999999% data reliability and up to 99.99% service availability, with complete automatic data backup and lossless recovery mechanisms.
TencentDB for MySQL supports strong synchronous data replication, and its kernel has been optimized to greatly improve data replication performance and effectively solve phantom read and temporary transaction issues.
TencentDB for MySQL supports strong synchronous data replication, and its kernel has been optimized to greatly improve data replication performance and effectively solve phantom read and temporary transaction issues.
The console provides more than 70 important metrics, which can be used to compare the instance running load in multiple dimensions through custom monitoring views.
The console provides more than 70 important metrics, which can be used to compare the instance running load in multiple dimensions through custom monitoring views.
Custom resource threshold alarms can report issues to Ops personnel promptly, helping users know the running status of instances and respond to problems quickly.
Custom resource threshold alarms can report issues to Ops personnel promptly, helping users know the running status of instances and respond to problems quickly.
TencentDB for MySQL perfectly adapts to TencentDB for DBbrain, realizing intelligent Ops and effectively ensuring secure, stable, and efficient operation of database services.
TencentDB for MySQL perfectly adapts to TencentDB for DBbrain, realizing intelligent Ops and effectively ensuring secure, stable, and efficient operation of database services.
With Data Transfer Service (DTS), automatic database migration is provided, which greatly simplifies database cloud migration and realizes seamless business migration to the cloud.
With Data Transfer Service (DTS), automatic database migration is provided, which greatly simplifies database cloud migration and realizes seamless business migration to the cloud.
Intra-city multi-AZ DR/cross-city DR guarantees HA. If a fault causes service interruption, businesses can be switched to the DR instance quickly to achieve database DR.
Intra-city multi-AZ DR/cross-city DR guarantees HA. If a fault causes service interruption, businesses can be switched to the DR instance quickly to achieve database DR.
Users can create a production-level MySQL database with simple clicks in the console, which is ready to use out of the box, and fine configuration and tuning features are provided.
With leading I/O throughput and a deeply customized and developed MySQL kernel, the performance of TencentDB for MySQL far exceeds self-built databases. It has a simplified backend architecture, which is easier to maintain and manage.
TencentDB for MySQL provides 99.9999999% data reliability and up to 99.99% service availability, with complete automatic data backup and lossless recovery mechanisms.
TencentDB for MySQL supports strong synchronous data replication, and its kernel has been optimized to greatly improve data replication performance and effectively solve phantom read and temporary transaction issues.
The console provides more than 70 important metrics, which can be used to compare the instance running load in multiple dimensions through custom monitoring views.
Custom resource threshold alarms can report issues to Ops personnel promptly, helping users know the running status of instances and respond to problems quickly.
TencentDB for MySQL perfectly adapts to TencentDB for DBbrain, realizing intelligent Ops and effectively ensuring secure, stable, and efficient operation of database services.
With Data Transfer Service (DTS), automatic database migration is provided, which greatly simplifies database cloud migration and realizes seamless business migration to the cloud.
Intra-city multi-AZ DR/cross-city DR guarantees HA. If a fault causes service interruption, businesses can be switched to the DR instance quickly to achieve database DR.
Databases are critical to core business operations, and data serves as the essential asset and lifeline of an enterprise. Ensuring stable production and operations requires a highly available database architecture. Database failures, data losses, or downtime can result in severe business impact and financial losses for an enterprise. TencentDB for MySQL offers an All-Scenario High Availability Architecture (AS-HAA). This architecture provides end-to-end and full-process safeguards to ensure business stability.
In gaming scenarios, players have long online sessions, and the business lifecycle is extended. Operations are mostly partitioned servers, resulting in large data volumes and stringent requirements for low latency. Furthermore, gaming services require extremely high availability to prevent server downtime and data loss. Rollback operations are critical in gaming, requiring a balance between efficiency and data integrity while minimizing the impact on users.
In e-commerce scenarios, sudden traffic surges can place immense pressure on server resources, requiring a highly scalable and flexible database architecture. High-concurrency access to hot data also requires support from a high-performance, highly available architecture. In addition, e-commerce operations typically involve large data volumes, posing performance demands for multi-table join queries and requiring real-time responsiveness.
Key challenges for financial services in database architecture include high security, processing of large data volumes, high performance, high availability, and high scalability. Additional complexities include complex query management, transaction isolation, and transaction optimization. The architecture must be designed to adhere to rigorous regulatory and compliance standards, guaranteeing data integrity, stability, and reliability.
The pain points of personal websites and SaaS scenarios in the database architecture include persistent data storage and data security. In addition, various user queries and data analysis requirements need to be handled.
Frequently Asked
Questions
TencentDB for MySQL is a high-performance enterprise-level database service professionally built by Tencent Cloud based on the world's most popular open-source database MySQL. It is 100% compatible with the MySQL protocol and is suitable for relational database scenarios.
TencentDB for MySQL can be used wherever the MySQL database is applicable. TencentDB for MySQL is more convenient and reliable than self-built MySQL databases.
TencentDB for MySQL is fully compatible with the MySQL protocol and provides primary-secondary hot backup and scheduled cold backup services. In addition, it supports seamless instance upgrades, which can minimize developers' investment in deployment, monitoring, scale-out, and fault recovery and allow them to focus on product development and operations.
TencentDB for MySQL uses MySQL versions 5.6, 5.7, and 8.0.
TencentDB for MySQL can be purchased on the official website and using APIs: Creating an Instance (Yearly/Monthly Subscription) and Creating an Instance (Pay-as-You-Go) .
Prepaid: Generally, it is a yearly/monthly subscription purchase form, that is, users should pay for fees before use. The system calculates the purchase amount based on the type and quantity of cloud services selected by a user and deducts the amount from the user's account.
Postpaid (also known as pay-as-you-go): Resources are applied for first as required, and fees are charged based on actual resource usage during settlement. Fees are settled based on the resource settlement cycle.
How to select: It is recommended that you select the prepaid mode if the business scenario is stable and cloud resources need to be used for a long time. It is recommended that you select the postpaid mode if business development fluctuates greatly and cannot be accurately predicted, or if the resource use is temporary and sudden.
When you purchase a TencentDB for MySQL instance, Tencent Cloud provides you with a price calculator . You can calculate the price in the calculator.
Private IP address: It is the connection address used to provide services to clients with private IP addresses.
Public IP address: It is the connection address for connecting to clients with public IP addresses.
They can be directly mapped to each other through network address translation.
Servers in the same region can communicate with each other through a private network. Servers in different regions can only communicate with each other through the public network.
Tencent Cloud Private Network (VPC) is a logically isolated network space that you customize on Tencent Cloud. Similar to the traditional network running in your data center, it manages your service resources on Tencent Cloud, including Cloud Virtual Machine (CVM) instances, Cloud Load Balancer (CLB) instances, and TencentDB for MySQL instances. Through VPC, data can be shared between TencentDB for MySQL instances and CVM instances in different regions.
In an application scenario with a small number of write requests but a large number of read requests to the database, one instance may not be able to resist the read load and may even affect the main business. To elastically scale out the reading capabilities to share the database load, you can create one or more read-only instances in a region and use the read-only instances to handle a large number of database read requests, thereby increasing the application throughput.
In scenarios with strong requirements for business continuity and data reliability or regulatory requirements, TencentDB for MySQL provides DR instances to help users improve business continuity capabilities at low costs and improve data reliability. A DR instance is a database backup of the primary instance.
Read-only instances can only be enabled for the primary database of MySQL 5.6 (GTID) or later.
When a read-only instance is created, two different engines, that is, the InnoDB engine and the LibraDB engine can be selected. The InnoDB engine can handle more concurrent read requests that the primary instance cannot carry under traditional circumstances. The LibraDB engine processes complex SQL statements in businesses, such as multi-table joins, group by of big data, and subqueries through columnar storage and parallel engines. If you create a read-only instance with a database containing MyISAM tables, MyISAM tables are converted to InnoDB tables forcibly during creation.
To create a DR instance, the primary instance should be MySQL 5.6 or later, and the GTID feature should be enabled.
Different regions of Tencent Cloud are isolated to ensure maximum stability and fault tolerance between different regions. Covered regions include:
China: South China, East China, North China, Southwest China, and Hong Kong (China).
Other countries: Southeast Asia Pacific, Northeast Asia Pacific, Western United States, Eastern United States, Europe, South America, and the Middle East.
We will gradually increase the regions to cover more nodes. It is recommended that users select the region closest to their customers, which can reduce the access latency and increase the download speed.
Select a region close to your users. Please select a TencentDB for MySQL region based on the geographical locations of your users. The closer the TencentDB for MySQL instance is to the access customers, the smaller the access latency and the higher the access speed. Example: If most of your users are located near the Yangtze River Delta, Shanghai is a better choice.
Select a region based on the principle of private network communication in the same region. Private networks in the same region can communicate with each other. Private networks in different regions cannot communicate with each other. When you purchase a TencentDB for MySQL instance, it is recommended that you select the region of your CVM instance to reduce access latency.
What is the isolation degree between AZs? AZs run in their independent and physically different facilities and are designed to be highly reliable. AZs do not share common failure points, such as generators and cooling equipment. In addition, they are physically independent of each other. Even if extremely rare disasters, such as fires, tornadoes, or floods, occur in an AZ, only this AZ is affected.
Frequently Asked
Questions
TencentDB for MySQL is a high-performance enterprise-level database service professionally built by Tencent Cloud based on the world's most popular open-source database MySQL. It is 100% compatible with the MySQL protocol and is suitable for relational database scenarios.
TencentDB for MySQL can be used wherever the MySQL database is applicable. TencentDB for MySQL is more convenient and reliable than self-built MySQL databases.
TencentDB for MySQL is fully compatible with the MySQL protocol and provides primary-secondary hot backup and scheduled cold backup services. In addition, it supports seamless instance upgrades, which can minimize developers' investment in deployment, monitoring, scale-out, and fault recovery and allow them to focus on product development and operations.
TencentDB for MySQL uses MySQL versions 5.6, 5.7, and 8.0.
TencentDB for MySQL can be purchased on the official website and using APIs: Creating an Instance (Yearly/Monthly Subscription) and Creating an Instance (Pay-as-You-Go) .
Prepaid: Generally, it is a yearly/monthly subscription purchase form, that is, users should pay for fees before use. The system calculates the purchase amount based on the type and quantity of cloud services selected by a user and deducts the amount from the user's account.
Postpaid (also known as pay-as-you-go): Resources are applied for first as required, and fees are charged based on actual resource usage during settlement. Fees are settled based on the resource settlement cycle.
How to select: It is recommended that you select the prepaid mode if the business scenario is stable and cloud resources need to be used for a long time. It is recommended that you select the postpaid mode if business development fluctuates greatly and cannot be accurately predicted, or if the resource use is temporary and sudden.
When you purchase a TencentDB for MySQL instance, Tencent Cloud provides you with a price calculator . You can calculate the price in the calculator.
Private IP address: It is the connection address used to provide services to clients with private IP addresses.
Public IP address: It is the connection address for connecting to clients with public IP addresses.
They can be directly mapped to each other through network address translation.
Servers in the same region can communicate with each other through a private network. Servers in different regions can only communicate with each other through the public network.
Tencent Cloud Private Network (VPC) is a logically isolated network space that you customize on Tencent Cloud. Similar to the traditional network running in your data center, it manages your service resources on Tencent Cloud, including Cloud Virtual Machine (CVM) instances, Cloud Load Balancer (CLB) instances, and TencentDB for MySQL instances. Through VPC, data can be shared between TencentDB for MySQL instances and CVM instances in different regions.
In an application scenario with a small number of write requests but a large number of read requests to the database, one instance may not be able to resist the read load and may even affect the main business. To elastically scale out the reading capabilities to share the database load, you can create one or more read-only instances in a region and use the read-only instances to handle a large number of database read requests, thereby increasing the application throughput.
In scenarios with strong requirements for business continuity and data reliability or regulatory requirements, TencentDB for MySQL provides DR instances to help users improve business continuity capabilities at low costs and improve data reliability. A DR instance is a database backup of the primary instance.
Read-only instances can only be enabled for the primary database of MySQL 5.6 (GTID) or later.
When a read-only instance is created, two different engines, that is, the InnoDB engine and the LibraDB engine can be selected. The InnoDB engine can handle more concurrent read requests that the primary instance cannot carry under traditional circumstances. The LibraDB engine processes complex SQL statements in businesses, such as multi-table joins, group by of big data, and subqueries through columnar storage and parallel engines. If you create a read-only instance with a database containing MyISAM tables, MyISAM tables are converted to InnoDB tables forcibly during creation.
To create a DR instance, the primary instance should be MySQL 5.6 or later, and the GTID feature should be enabled.
Different regions of Tencent Cloud are isolated to ensure maximum stability and fault tolerance between different regions. Covered regions include:
China: South China, East China, North China, Southwest China, and Hong Kong (China).
Other countries: Southeast Asia Pacific, Northeast Asia Pacific, Western United States, Eastern United States, Europe, South America, and the Middle East.
We will gradually increase the regions to cover more nodes. It is recommended that users select the region closest to their customers, which can reduce the access latency and increase the download speed.
Select a region close to your users. Please select a TencentDB for MySQL region based on the geographical locations of your users. The closer the TencentDB for MySQL instance is to the access customers, the smaller the access latency and the higher the access speed. Example: If most of your users are located near the Yangtze River Delta, Shanghai is a better choice.
Select a region based on the principle of private network communication in the same region. Private networks in the same region can communicate with each other. Private networks in different regions cannot communicate with each other. When you purchase a TencentDB for MySQL instance, it is recommended that you select the region of your CVM instance to reduce access latency.
What is the isolation degree between AZs? AZs run in their independent and physically different facilities and are designed to be highly reliable. AZs do not share common failure points, such as generators and cooling equipment. In addition, they are physically independent of each other. Even if extremely rare disasters, such as fires, tornadoes, or floods, occur in an AZ, only this AZ is affected.