1
00:00:00,000 --> 00:00:09,180
[Music]

2
00:00:09,180 --> 00:00:09,680
In this unit,

3
00:00:10,175 --> 00:00:14,820
we will talk about the reasons for choosing 
TiDB, as well as showing some of the TiDB users.

4
00:00:16,140 --> 00:00:19,380
Many customers choose TiDB 
due to these two reasons.

5
00:00:20,220 --> 00:00:25,020
The first one is “scalable”. TiDB is 
scalable for mission critical workloads.

6
00:00:25,680 --> 00:00:28,860
TiDB provides horizontal scalability, meaning that  

7
00:00:28,860 --> 00:00:34,620
TiDB supports zero downtime scaling in and 
scaling out at every sub-component layer,  

8
00:00:34,620 --> 00:00:40,380
which includes the computation layer, the 
storage layer, and metadata layer. These  

9
00:00:40,380 --> 00:00:45,120
layers are decoupled from each other and can 
be scaled on demand without any disruptions.

10
00:00:45,840 --> 00:00:51,480
By using TiDB, you may eliminate both planned 
and unplanned downtime. In addition to the  

11
00:00:51,480 --> 00:00:56,100
scaling in and scaling out mentioned before, 
TiDB also supports online rolling updates  

12
00:00:56,100 --> 00:01:02,580
and online DDL. Its built-in self-healing 
ability is enabled at the compute, storage,  

13
00:01:02,580 --> 00:01:08,100
and metadata layers, ensuring the business 
continuity when faced with software failures,  

14
00:01:08,100 --> 00:01:12,000
hardware malfunctions, and 
even a data center outages.  

15
00:01:12,600 --> 00:01:17,580
In addition, users can enjoy these benefits 
on TiDB Cloud with no additional setup.

16
00:01:18,180 --> 00:01:20,460
Similar to traditional RDBMS,  

17
00:01:20,460 --> 00:01:25,040
TiDB offers full ACID transactional 
support with strong consistency.

18
00:01:25,040 --> 00:01:30,600
TiDB is compatible with MySQL 
5.7, meaning that in most cases,  

19
00:01:30,600 --> 00:01:36,060
you can migrate your existing applications to TiDB 
without the need to alter the application code.  

20
00:01:37,260 --> 00:01:41,760
It has already been proven in production 
that consolidating hundreds or even  

21
00:01:41,760 --> 00:01:46,500
thousands of MySQL-compatible databases 
into a single TiDB cluster is possible.

22
00:01:47,340 --> 00:01:52,320
The second reason for choosing TiDB is the 
built-in Translytical, or HTAP, capability,  

23
00:01:52,320 --> 00:01:58,020
meaning TiDB is able to deal with transactional 
and analytical transactions at the same time.

24
00:01:58,800 --> 00:02:03,000
TiDB is equipped with both row-based 
and columnar-based storage engines,  

25
00:02:03,000 --> 00:02:06,600
making it optimized for handling both OLTP and  

26
00:02:06,600 --> 00:02:11,160
analytical workloads simultaneously. 
With a single standard SQL interface,  

27
00:02:11,160 --> 00:02:17,640
business analysts can easily gain insights from 
both online operations and cold data combined.

28
00:02:17,640 --> 00:02:23,700
TiDB is able to efficiently store and retrieve 
a large amount of data at the PB scale.  

29
00:02:23,700 --> 00:02:29,760
TiDB simplifies handling of most Big Data 
issues with its implementation of standard SQL,  

30
00:02:29,760 --> 00:02:36,660
and with the added support for JSON data type and 
functions, it eliminates the need to incorporate  

31
00:02:36,660 --> 00:02:43,020
specialized tools from the Big Data ecosystem. 
As a result, SQL is back in the driver's seat.

32
00:02:43,980 --> 00:02:50,100
TiDB encapsulates the complexity of No One 
Size Fits All and reduces the re-investment,  

33
00:02:50,100 --> 00:02:56,160
especially the re-investment in the Cloud. 
In the field of databases, it has been widely  

34
00:02:56,160 --> 00:03:01,800
accepted for many years that there is no universal 
solution that fits all since varying applications  

35
00:03:01,800 --> 00:03:07,260
have their unique database requirements. While 
some require high availability and scalability,  

36
00:03:07,260 --> 00:03:13,260
others demand high performance and low latency. 
Furthermore, different database technologies and  

37
00:03:13,260 --> 00:03:19,440
configurations offer distinct advantages 
and limitations. Thus, it is essential to  

38
00:03:19,440 --> 00:03:25,080
comprehend the specific needs of your application 
and select the appropriate database technology and  

39
00:03:25,080 --> 00:03:31,560
configuration that optimally addresses those 
requirements. However, this often leads to a  

40
00:03:31,560 --> 00:03:36,660
significant increase in management complexity, 
which can be further amplified in public cloud  

41
00:03:36,660 --> 00:03:43,020
environments because of reinvestment issues. At 
TiDB's core, it is a key-value NoSQL database that  

42
00:03:43,020 --> 00:03:49,500
incorporates a stateless SQL layer, granting 
it the advantages of both NoSQL and RDBMS.  

43
00:03:51,360 --> 00:03:56,640
It has been designed to handle the complexities 
associated with combining these two technologies,  

44
00:03:56,640 --> 00:04:02,880
adhering to the principle of "No One 
Size Fits All" at a lower level. However,  

45
00:04:02,880 --> 00:04:08,640
at the higher operation level, TiDB presents a 
single management interface as a unified database,  

46
00:04:08,640 --> 00:04:15,300
enabling users to benefit from both approaches 
simultaneously. Unless your application requires  

47
00:04:15,300 --> 00:04:20,760
extremely low latency, otherwise for most of 
the cases, TiDB is a comprehensive solution.

48
00:04:22,980 --> 00:04:29,220
As mentioned earlier, TiDB offers both row-based 
and column-based storage engines. The column-based  

49
00:04:29,220 --> 00:04:33,960
engine is capable of automatically replicating 
the necessary data from the row-based engine  

50
00:04:33,960 --> 00:04:38,340
for analytical workloads, without 
the need for additional ETL jobs.

51
00:04:39,360 --> 00:04:46,560
TiDB is used by more than 3,000 global adopters, 
and it is trusted by global innovation leaders.

52
00:04:46,560 --> 00:04:48,480
Here are a few examples.

53
00:04:50,400 --> 00:04:54,660
Catalyst is a Software-as-a-Service (SaaS) 
company that provides a powerful customer  

54
00:04:54,660 --> 00:04:58,800
success platform to help companies 
achieve success with their customers.

55
00:04:59,760 --> 00:05:06,120
Catalyst used PostgreSQL, and then Elasticsearch 
for their data backends, but did not work out.

56
00:05:06,720 --> 00:05:13,440
Then, Catalyst investigated TiDB. They found 
that TiDB’s response time was 10 to 60 times  

57
00:05:13,440 --> 00:05:20,760
faster than its competitors. Also they are keen 
that TiDB has perfect support for online DDL.

58
00:05:21,420 --> 00:05:26,460
Bolt is a global mobility company headquartered 
in Estonia that mainly offers vehicle hiring,  

59
00:05:26,460 --> 00:05:31,920
car-sharing, and food delivery 
services. Bolt has over 100 million customers.

60
00:05:32,580 --> 00:05:37,680
Previously, Bolt used MySQL as its main 
database. As the data volume grows,  

61
00:05:37,680 --> 00:05:41,220
sharding was introduced, and 
did not meet their expectations.

62
00:05:42,060 --> 00:05:46,500
Bolt explored Vitess and TiDB 
for the MySQL replacement. It  

63
00:05:46,500 --> 00:05:50,400
turned out that Vitess required too 
many changes to Bolt’s applications.  

64
00:05:51,240 --> 00:05:55,620
Bolt finally chose TiDB, an open 
source, distributed NewSQL database.

65
00:05:56,520 --> 00:06:00,840
Bolt is impressed by TiDB’s almost 
infinite horizontal scalability.  

66
00:06:00,840 --> 00:06:04,080
By automatically adding or removing storage nodes,  

67
00:06:04,080 --> 00:06:09,540
it can easily handle up to hundreds of 
terabytes of sudden data spikes or plunges.

68
00:06:10,380 --> 00:06:15,480
Moreover, TiDB has strong compression 
capability, which reduces storage costs.

69
00:06:16,380 --> 00:06:19,500
Lastly, it has a simplified 
architecture and can handle  

70
00:06:19,500 --> 00:06:22,560
transactional and analytical 
workloads at the same time.

71
00:06:24,360 --> 00:06:29,400
You may go to https://www.pingcap.com/customers/ 
for more use cases.