TiDB VS MySQL

author ： Ann_ann The source of the original ：https://tidb.net/blog/6035684e

Characteristics of an ideal database

• Strong consistency and high availability ;
• High throughput 、 High concurrency 、 Low latency ;
• standard SQL、 Support ACID Business ;
• Big data is ecologically friendly ;
• Ability to expand horizontally , And try not to intrude into the business ;

Database architecture selection

TiDB And MySQL contrast

TiDB and MySQL Compatibility policy

May refer to ：https://docs.pingcap.com/zh/tidb/stable/mysql-compatibility

By 4.0 edition ,TiDB And MySQL Summary of the differences ：

Solutions for massive data and large tables

• MySQL We need to divide the databases and tables , Business development and DBA Work together and solve this problem slightly inefficiently ;
• TiDB A single table is almost infinite （ The industry already exists 100 More than 100 million watches ）.

Database cluster is highly available

• MySQL You need to manually investigate and deploy high availability clusters , And different high availability schemes have different maintenance methods ;
• TiDB Built in high availability architecture , Automatic disaster recovery .

MySQL Sub database and sub table VS TiDB

summary

TiDB  The goal of the design is to  MySQL  The scenario of separating databases and tables due to the capacity limitation of a single machine , Or scenarios that require strong consistency and complete distributed transactions .TiDB The advantage of is to push down to the storage node for parallel computing . For small watches （ For example, below tens of millions ）, Not suitable for  TiDB, Because of the small amount of data ,Region  Co., LTD. , Can't take advantage of parallelism .