EN: |+| Music |+| In this unit, we are going to talk about two real world use cases. EN: |+| Let's first look at company A. EN: Company A is one of the most famous social media companies |+| in the world. EN: Company A has more than 1.2 million QPS and more than 9 billion accounts. EN: |+| HBase was used to support more than 100 business use cases. EN: |+| Company A's HBase clusters have 9,000 VMs, |+| 50 production clusters, and 6 PBs of data. EN: |+| One of the most typical HBase use cases is to record the administration history. EN: |+| The administration history records user rule violations, |+| the subsequent actions taken against the user and the timelines for each action. EN: |+| The support for transaction is necessary to prevent repetitive |+| punishments and guarantee the accuracy of the publicly available transparent report. EN: |+| The first generation of solution was to use HBase, |+| as well as many in-house systems, such as index service and transaction service, |+| which provides the functionalities unavailable in HBase. EN: However, this leads to high costs, |+| including high maintenance cost and high infra cost for complicated systems. EN: |+| Moreover, not all of the missing functionalities can be addressed |+| with a workaround, such as cross table strong consistency transaction. EN: |+| In addition to that, it is very hard to upgrade HBase to the latest versions. EN: |+| In the second generation solutions, Company A uses TiDB to replace HBase. EN: |+| TiDB natively supports index management and transaction control. EN: |+| After switching to TiDB, Company A is thrilled to find out that there is 3 to 5 times 99-percentile |+| query latency reduction. EN: TiDB also provides standard SQL interface with native support of |+| cross-table strong consistency transactions. EN: The operation tasks have also been greatly simplified. EN: |+| Let's now look at company B. EN: Company B is a mobile gaming and internet service provider, |+| which offers gaming services to multiple regions around the world. EN: |+| Company B has more than 50 million users worldwide. EN: |+| In Company B, various independent databases serve specific business modules respectively, |+| for example, audience, rewards and user tags management. EN: Those data are used for gaming |+| campaigns and user conversions, which is of great importance for Company B. EN: |+| Currently, analytics across multiple databases is |+| necessary to effectively manage advertising and conversions. EN: |+| In the first generation of the solution, multiple Amazon Aurora RDS instances are |+| used for conducting transactional queries: one Amazon Aurora instance for each business module. EN: |+| There is also a single Amazon Redshift database used to perform analytical queries. EN: |+| As the data volume increases, when the data volume of a single table |+| increases to 100 million rows, maintenance becomes difficult. EN: |+| There are three main challenges. EN: |+| The first one is that, additional ETL jobs are needed, and Amazon Redshift |+| is not effective in handling data updates in real-time. EN: Due to the increase in data volume, |+| the solution was unable to meet the real-time advertising requirements. EN: |+| Secondly, updating and maintaining Aurora RDS is hard. EN: The ops team |+| could only do maintenance in the middle of the night. EN: |+| Thirdly, Online Data Definition Language (DDL) operations with Aurora are inefficient. EN: Online |+| DDL with Aurora usually took hours and sometimes failed due to lack of resources. EN: |+| After switching to TiDB Cloud, one TiDB cluster is enough to replace |+| multiple Amazon Aurora clusters, as well as the Amazon Redshift cluster. EN: |+| The throughput is three times more than that of Aurora, |+| with query and write capabilities both improved. EN: |+| TiDB Cloud also supports horizontal scalability, strong consistency, and high availability. EN: |+| There is no data latency issue with the gaming platform. EN: At the same time, TiDB's built-in |+| columnar storage, TiFlash, improves analytics performance without changing the application. EN: |+| The operation task has been significantly simplified, and there is no application changes |+| That marks the end of the Introduction to TiDB course. EN: Thanks for staying with me. EN: |+| If you would like to learn more, please visit the PingCAP Training and Certification home page. EN: |+| I am sure you can find a course or workshop that suits you.