open-source NewSQL database that supports HTAP workloads. It is MySQL compatible and features horizontal scalability, strong consistency, and high availability. The goal of TiDB is to provide users with 运单系统 (Exadata to TiDB) ZTO - 运单系统 (Exadata to TiDB) ZTO - 运单系统 (Exadata to TiDB) • Unlimited Scalability • Not more sharding “分库分表达到 16000 张表，业务上已经⽆法再继续扩展下去” • Greatly reduced the workload of business architectural evolution direction TiDB Core Architecture Goal: • Better cost efficiency • Faster scalability • Higher availability Direction: • Cloud native • Take fully advantage of cloud infrastructures

19 Vertical Sharding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Horizontal Sharding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 8.1.2 Challenges distributed scenarios. It provides the capabilities necessary for distributed systems, such as horizontal scaling of computing capability and high availability. Clustered environments need to store metadata threshold and evacuate the traffic. Sharding method can be divided into vertical sharding and horizontal sharding. Vertical Sharding According to business sharding method, it is called vertical sharding

Architecture Evolution • Lessons Learned • Open Source Community Design Goals Goal 1: Horizontal Scalability Goal 2: High Availability Goal 3: ACID Transaction SQL at Scale select count(*) from

Slave Master Slave •Open-source NewSQL database •High availability •Strong consistency •Horizontal scalability •Support the MySQL wire protocol https://github.com/pingcap/tidb
 TiDB Overview MySQL

support, Apache httpd can now run in a hybrid multiprocess, multithreaded mode. This improves scalability for many, but not all configurations. New Build System The build system has been rewritten from Compared to Apache 1.3, release 2.x contains many additional optimizations to increase throughput and scalability. Most of these improvements are enabled by default. However, there are compile-time and run-time systems, there are several MPMs from which to choose. The choice of MPM can affect the speed and scalability of the httpd: The worker MPM uses multiple child processes with many threads each. Each thread

format ● An HTAP database needs to store huge amount of data ● Scalability is very important ● TiDB relies on multi-raft for scalability ○ One command to add / remove node ○ Scaling is fully automatic automatic ○ Smooth and painless data rebalance ● TiFlash adopts the same design Scalability ● Perfect Resource Isolation ● Data rebalance based on the “label” mechanism ○ Dedicated nodes for TiFlash /

support, Apache httpd can now run in a hybrid multiprocess, multithreaded mode. This improves scalability for many, but not all configurations. New Build System The build system has been rewritten from Compared to Apache 1.3, release 2.x contains many additional optimizations to increase throughput and scalability. Most of these improvements are enabled by default. However, there are compile-time and run-time systems, there are several MPMs from which to choose. The choice of MPM can affect the speed and scalability of the httpd: The worker MPM uses multiple child processes with many threads each. Each thread

support, Apache httpd can now run in a hybrid multiprocess, multithreaded mode. This improves scalability for many, but not all configurations. New Build System The build system has been rewritten from Compared to Apache 1.3, release 2.x contains many additional optimizations to increase throughput and scalability. Most of these improvements are enabled by default. However, there are compile-time and run-time systems, there are several MPMs from which to choose. The choice of MPM can affect the speed and scalability of the httpd: The worker MPM uses multiple child processes with many threads each. Each thread

support, Apache httpd can now run in a hybrid multiprocess, multithreaded mode. This improves scalability for many, but not all configurations. New Build System The build system has been rewritten from Compared to Apache 1.3, release 2.x contains many additional optimizations to increase throughput and scalability. Most of these improvements are enabled by default. However, there are compile-time and run-time systems, there are several MPMs from which to choose. The choice of MPM can affect the speed and scalability of the httpd: The worker MPM uses multiple child processes with many threads each. Each thread

support, Apache httpd can now run in a hybrid multiprocess, multithreaded mode. This improves scalability for many, but not all configurations. New Build System The build system has been rewritten from Compared to Apache 1.3, release 2.x contains many additional optimizations to increase throughput and scalability. Most of these improvements are enabled by default. However, there are compile-time and run-time systems, there are several MPMs from which to choose. The choice of MPM can affect the speed and scalability of the httpd: The worker MPM uses multiple child processes with many threads each. Each thread