TiDB (The pronunciation is: /'taɪdiːbi:/ tai-D-B, etymology: titanium) is a Hybrid Transactional/Analytical Processing (HTAP) database. Inspired by the design of Google F1 and Google Spanner, TiDB features infinite horizontal scalability, strong consistency, and high availability. The goal of TiDB is to serve as a one-stop solution for online transactions and analyses.
- Horizontal scalability
Grow TiDB as your business grows. You can increase the capacity for storage and computation simply by adding more machines.
- Compatible with MySQL protocol
Use TiDB as MySQL. You can replace MySQL with TiDB to power your application without changing a single line of code in most cases.
- Automatic Failover and high availability
Your data and applications are always-on. TiDB automatically handles malfunctions and protects your applications from machine failures or even downtime of an entire data-center.
- Consistent distributed transactions
Think of TiDB as a single-machine RDBMS. You can start a transaction that crosses multiple machines without worrying about consistency. TiDB makes your application code simple and robust.
- Online DDL
Evolve TiDB schemas as your requirement changes. You can add new columns and indexes without stopping or affecting the on-going operations.
- Multiple storage engine support
Power TiDB with your most favorite engines. TiDB supports local storage engines such as GolevelDB, as well as TiKV, a distributed storage engine.
For more details, see How we build TiDB.
You can view the list of TiDB adopters here.
Read the Roadmap.
Read the Quick Start.
Contributions are welcomed and greatly appreciated. See CONTRIBUTING.md for details on submitting patches and the contribution workflow.
- Twitter: @PingCAP
- Reddit: https://www.reddit.com/r/TiDB/
- Stack Overflow: https://stackoverflow.com/questions/tagged/tidb
- Mailing list: Google Group
TiDB is under the Apache 2.0 license. See the LICENSE file for details.