EN: |+| When we talk about TiDB, why do we call it a distributed database?

EN: Before we dive deep into the architecture, |+| I want to give you a quick answer to another straightforward question - why we should use TiDB?

EN: |+| When you start to use TiDB you will soon realize following benefits.

EN: First, seamless scalability.

EN: |+| In TiDB, all key components are decoupled with each other and support horizontal scalability.

EN: |+| For high availability in the disaster recovery, for those stateful components, consistent data |+| replications are supported you can achieve High Availability easily by deploying multiple such |+| components, or achieve Disaster Recovery by deploying them across Geographic locations.

EN: |+| Third, TiDB is actually a horizontal scalable NoSQL database with SQL and |+| transaction compatibility.

EN: By using TiDB, you gain benefits of NoSQL and SQL at the same time.

EN: |+| And, your database can grow into massive magnitude volume that MySQL database |+| cannot even image.

EN: For auto sharding, the way TiDB achieves it doesn't need application changes.

EN: Last, |+| by using TiDB and by using standard SQL only you already have the ticket to the Big Data party |+| no ETL or extract, transformation ,load required.

EN: TiDB can almost store and retrieve any amount of data.

EN: And, |+| it provides both row based store and the columnar store suitable for transaction processing and |+| analytical processing at the same time.

EN: I'm going to cover it in more detail in this course later.