10 Reasons Why the TiDB Database Should Power Your Next Development Project
summary
The talk claims TiDB actually combines OLTP and OLAP in one system by pairing row store TiKV with columnar TiFlash and a PD metadata/timestamp service; it uses MySQL protocol, JDBC/ODBC, TiCDC for change capture, BR/Lightning for backup/import, and a cloud offering. It ships open source, defaults to three replicas by default, auto-splits regions around ~144MB, and supports automatic rebalancing and no manual sharding while TiDB servers scale statelessly.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:08Application Users
- 1:41Connect with Odbc
- 5:48Placement Driver
- 9:26Open Source
- 10:31Mysql Connectivity
- 11:56Component Based
- 13:46Backup and Recovery
- 17:23Should You Use Sharding
- 25:26Splitting of Data into the Multiple Regions
- 28:55Robust Optimizer
- 35:56Compute and Storage
- 43:51Fraud Detection
related talks
29mDistributed SQL How TiDB Modernized Data Management
29mDistributed SQL: How TiDB Modernized Data Management
46mTiDB 101
33mProvisioning the Distributed Database TiDB on Kubernetes
36mHow Can HTAP Databases Simplify Your Data Infrastructure?
18mTiFlash: Make TiKV 10x Faster and HTAP-able
24mUsing a Distributed Key-Value Store
28mTaming Billions of Rows: Data Lifecycle Management Lessons From a Cloud Native Database…