1
00:00:07,006 --> 00:00:16,680
When we talk about TiDB, why do we call it a distributed 
database? Before we dive deep into the architecture,  

2
00:00:16,680 --> 00:00:24,180
I want to give you a quick answer to another 
straightforward question - why we should use TiDB? 

3
00:00:24,780 --> 00:00:32,340
When you start to use TiDB you will soon realize 
following benefits. First, seamless scalability.  

4
00:00:32,340 --> 00:00:40,020
In TiDB, all key components are decoupled with 
each other and support horizontal scalability.  

5
00:00:40,620 --> 00:00:47,640
For high availability in the disaster recovery, 
for those stateful components, consistent data  

6
00:00:47,640 --> 00:00:53,640
replications are supported you can achieve High 
Availability easily by deploying multiple such  

7
00:00:53,640 --> 00:00:59,520
components, or achieve Disaster Recovery by 
deploying them across Geographic locations.  

8
00:01:00,120 --> 00:01:05,580
Third, TiDB is actually a horizontal 
scalable NoSQL database with SQL and  

9
00:01:05,580 --> 00:01:12,480
transaction compatibility. By using TiDB, you gain 
benefits of NoSQL and SQL at the same time.  

10
00:01:13,320 --> 00:01:19,680
And, your database can grow into massive 
magnitude volume that MySQL database  

11
00:01:19,680 --> 00:01:28,020
cannot even image. For auto sharding, the way TiDB
achieves it doesn't need application changes. Last,  

12
00:01:28,020 --> 00:01:35,280
by using TiDB and by using standard SQL only 
you already have the ticket to the Big Data party  

13
00:01:35,880 --> 00:01:46,020
no ETL or extract, transformation ,load required. TiDB can 
almost store and retrieve any amount of data. And,  

14
00:01:46,020 --> 00:01:52,380
it provides both row based store and the columnar 
store suitable for transaction processing and  

15
00:01:52,380 --> 00:01:58,260
analytical processing at the same time. I'm going 
to cover it in more detail in this course later.