What problem it solves

TiDB addresses the need for a database that supports transactional, analytical, and vector-search workloads while remaining available and consistent as infrastructure changes. Its distributed architecture separates computing from storage, supports scaling in either direction, and provides built-in mechanisms for replication and failover.

Key features

• Distributed Transactions — TiDB uses a two-phase commit protocol to provide ACID-compliant transactions across multiple nodes. Its distributed design is intended to maintain data correctness during network partitions or node failures.

  Source: README

• Scalability — TiDB can be scaled horizontally by adding nodes or vertically by increasing resources on existing nodes without downtime. Computing and storage can be adjusted independently.

  Source: README

• High Availability — Built-in Raft consensus supports automated failover, while multiple replicas and majority-write commits are used to maintain consistency and availability when replicas fail. Replica placement can be configured for different disaster-tolerance levels.

  Source: README

• Hybrid Transactional and Analytical Processing — TiDB combines the TiKV row-based storage engine with the TiFlash columnar storage engine. TiFlash replicates data from TiKV in real time, and the TiDB Server coordinates queries across both engines.

  Source: README

• Cloud-Native Deployment and MySQL Compatibility — TiDB can be deployed in public clouds, on-premises, or natively in Kubernetes, with TiDB Operator and TiDB Cloud supporting deployment and cluster operations. It is compatible with MySQL 8.0 and supports familiar protocols, frameworks, and tools.

  Source: README

Who it may suit

This project may suit teams building applications that need transactional and analytical SQL capabilities in a distributed, cloud-native database. It may also suit developers familiar with MySQL who want to migrate applications with minimal changes.

Topics to discuss

• How do you plan for scaling TiDB while balancing horizontal and vertical resource changes?

• Which deployment environment best fits your operational requirements: Kubernetes, on-premises, public cloud, or TiDB Cloud?

• What workload patterns have you tested for TiDB's HTAP and vector-search capabilities?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/pingcap/tidb#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.