- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide（InnoDB）
- Best Practice
- Security White Paper
- Development Guide
- InnoDB
- Overview
- Use Limits
- Compatibility
- Connecting Database
- Join and Subquery
- Sequence
- Frequently Used DML Statements
- Read/Write Separation
- Distributed Transaction
- Creating Table
- Connection Protection
- Globally Unique Field
- Exporting/Importing Data
- Database Management Statements
- Passthrough SQL
- Preprocessing
- Subpartitioning
- Error Codes and Messages
- InnoDB
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- TDSQL APIs
- CreateDedicatedClusterDCDBInstance
- DescribeDBTmpInstances
- DescribeLogFileRetentionPeriod
- UpgradeDedicatedDCDBInstance
- ActiveHourDCDBInstance
- CancelDcnJob
- CloneAccount
- CloseDBExtranetAccess
- CopyAccountPrivileges
- CreateAccount
- CreateDCDBInstance
- CreateHourDCDBInstance
- DeleteAccount
- DescribeAccountPrivileges
- DescribeAccounts
- DescribeDBLogFiles
- ModifyAccountConfig
- DescribeDBParameters
- DescribeDBSlowLogs
- DescribeDBSyncMode
- DescribeDCDBInstanceNodeInfo
- DescribeDCDBInstances
- DescribeDCDBPrice
- DescribeDCDBShards
- DescribeDatabaseObjects
- DescribeDatabaseTable
- DescribeDatabases
- DescribeDcnDetail
- DescribeFileDownloadUrl
- DescribeFlow
- DestroyDCDBInstance
- DestroyHourDCDBInstance
- GrantAccountPrivileges
- InitDCDBInstances
- IsolateDedicatedDBInstance
- IsolateHourDCDBInstance
- ModifyAccountDescription
- ModifyDBInstanceName
- ModifyDBInstancesProject
- ModifyDBParameters
- ModifyDBSyncMode
- ModifyInstanceVip
- ModifyInstanceVport
- OpenDBExtranetAccess
- ResetAccountPassword
- SwitchDBInstanceHA
- TerminateDedicatedDBInstance
- UpgradeHourDCDBInstance
- IsolateDCDBInstance
- DescribeDCDBInstanceDetail
- DescribeOrders
- Security Group APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- General References
- Glossary
- Announcements
- Contact Us
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide（InnoDB）
- Best Practice
- Security White Paper
- Development Guide
- InnoDB
- Overview
- Use Limits
- Compatibility
- Connecting Database
- Join and Subquery
- Sequence
- Frequently Used DML Statements
- Read/Write Separation
- Distributed Transaction
- Creating Table
- Connection Protection
- Globally Unique Field
- Exporting/Importing Data
- Database Management Statements
- Passthrough SQL
- Preprocessing
- Subpartitioning
- Error Codes and Messages
- InnoDB
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- TDSQL APIs
- CreateDedicatedClusterDCDBInstance
- DescribeDBTmpInstances
- DescribeLogFileRetentionPeriod
- UpgradeDedicatedDCDBInstance
- ActiveHourDCDBInstance
- CancelDcnJob
- CloneAccount
- CloseDBExtranetAccess
- CopyAccountPrivileges
- CreateAccount
- CreateDCDBInstance
- CreateHourDCDBInstance
- DeleteAccount
- DescribeAccountPrivileges
- DescribeAccounts
- DescribeDBLogFiles
- ModifyAccountConfig
- DescribeDBParameters
- DescribeDBSlowLogs
- DescribeDBSyncMode
- DescribeDCDBInstanceNodeInfo
- DescribeDCDBInstances
- DescribeDCDBPrice
- DescribeDCDBShards
- DescribeDatabaseObjects
- DescribeDatabaseTable
- DescribeDatabases
- DescribeDcnDetail
- DescribeFileDownloadUrl
- DescribeFlow
- DestroyDCDBInstance
- DestroyHourDCDBInstance
- GrantAccountPrivileges
- InitDCDBInstances
- IsolateDedicatedDBInstance
- IsolateHourDCDBInstance
- ModifyAccountDescription
- ModifyDBInstanceName
- ModifyDBInstancesProject
- ModifyDBParameters
- ModifyDBSyncMode
- ModifyInstanceVip
- ModifyInstanceVport
- OpenDBExtranetAccess
- ResetAccountPassword
- SwitchDBInstanceHA
- TerminateDedicatedDBInstance
- UpgradeHourDCDBInstance
- IsolateDCDBInstance
- DescribeDCDBInstanceDetail
- DescribeOrders
- Security Group APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- General References
- Glossary
- Announcements
- Contact Us
Note:
TDSQL for MySQL is currently only applicable to OLTP business scenarios, such as transaction systems and frontend systems. It is not applicable to OLAP-based systems such as ERP and BI.
Large Applications (Real-time Transaction with Ultra-high Concurrency)
Service providers from ecommerce, finance, O2O, social networking, retail, and SaaS industries generally have the following problems restricting their business development: a large user base (million-level or higher), frequent marketing campaigns, and slower response from core trading system databases.
TDSQL for MySQL features linearly horizontal scalability that can increase the processing power of databases in real time for improved access efficiency. It can sustain over 15 million QPS at the peak, enabling you to cope with high-concurrence real-time transaction scenarios. For example, WeChat Pay, Tenpay, and Tencent Top-up are all supported by databases using the TDSQL for MySQL architecture.
IoT Data (Storage and Access of Petabytes of Data)
In typical IoT scenarios such as industrial monitoring and remote control, smart city, smart home, and IoV, a large number of sensing and monitoring devices, high sample rate, and massive storage capacity are required. Generally, petabytes to exabytes of data may be generated for storage per year. Traditional x86 server architecture and open-source database solutions cannot store or use such a huge amount of data at all.
TDSQL for MySQL features horizontal capacity expansion, helping you store massive amounts of data at lower costs than shared storage solutions.
File Index (Instant Access to Trillions of Data Rows)
Generally, a cloud service platform contains hundreds of millions to trillions of rows of image, document, and video data. It usually needs to store the indexes of such files to databases and perform real-time CRUD operations at the index level.
As the service platform sustains access requests from customers, extremely high service quality and performance are required. Traditional databases cannot support such access and use. TDSQL for MySQL boasts ultra-high performance, scalability, and strong sync capabilities, effectively ensuring the service quality and data consistency on the platform.
Cost-effective Commercial Database Solution
In order to support massive data storage and high-concurrence database access, large enterprises, and banks are extremely dependent on minicomputers and high-end storage. Internet companies can achieve the same or even higher capabilities of commercial databases with low-cost x86 servers and open-source software.
TDSQL for MySQL is suitable for various scenarios such as national or provincial business system aggregation, large ecommerce and channel platforms, internet banking services, and trading systems.
Yes
No
Was this page helpful?