TiDB

TiDB is an open-source distributed SQL database that combines a MySQL-compatible interface with horizontal scalability and strong ACID consistency across multiple nodes. It is designed for organizations that have outgrown single-node databases and need to handle both high-volume transactions (OLTP) and real-time analytics (OLAP) on a unified platform without manual sharding. The architecture separates compute from storage: TiDB servers handle SQL parsing and query planning, while TiKV (row-based storage) and TiFlash (columnar storage) manage data persistence. This separation allows independent scaling of compute and storage resources. TiDB uses the Raft consensus protocol for replication and fault tolerance, with placement rules that can pin Raft leaders closer to write-heavy regions to reduce latency. In independent benchmarks on comparable cloud instances (c5.4xlarge, three regions), TiDB achieved 52K TPS on OLTP mixed workloads, 95K QPS on read-heavy patterns, and 40K TPS on write-heavy patterns, with P99 write latencies of 30-80ms in geo-distributed setups. Its real-time analytics capability is rated as "Excellent" in the same benchmarks, significantly ahead of CockroachDB and YugabyteDB, thanks to TiFlash's columnar engine that bypasses row-based storage for analytical queries. The database is fully compatible with the MySQL wire protocol, meaning existing MySQL applications can often connect with minimal code changes. TiDB is available as a self-managed deployment or as a fully managed cloud service (TiDB Cloud) on AWS, Google Cloud, and Azure. The cloud offering includes a free Starter tier (25 GiB row storage, 25 GiB column storage, 2 vCPU) and a Dedicated tier with per-minute billing for compute nodes, starting at $0.4416/hour for a 4 vCPU TiDB node in us-west-2. TiDB is owned and operated by PingCAP, the original developer and current maintainer of the project.

TiDB's key capability is its hybrid transactional/analytical processing (HTAP) design, which lets users run real-time analytics directly on fresh transactional data without ETL pipelines. The TiFlash columnar storage engine replicates data from TiKV asynchronously, enabling sub-second analytical queries on the same cluster that handles OLTP writes. This eliminates the need for a separate data warehouse for many use cases. The database also supports advanced features like placement rules for data locality (e.g., pinning specific tables to certain regions for compliance or performance), automatic region-based sharding that rebalances data as nodes are added or removed, and a built-in dashboard for monitoring cluster health and query performance. TiDB Cloud adds automated backups, point-in-time recovery, and one-click vertical/horizontal scaling through a web console. The Dedicated tier allows selecting node sizes from 4 vCPU/16 GiB up to 32 vCPU/128 GiB for TiDB and TiKV, and up to 32 vCPU/256 GiB for TiFlash, with costs varying by cloud provider and region. For example, a 16 vCPU TiKV node costs $1.7664/hour on AWS in Oregon, while a 32 vCPU TiFlash node costs $3.5328/hour. The free Starter tier is sufficient for development and small-scale testing but is not recommended for production workloads.

In the distributed SQL market, TiDB competes directly with CockroachDB and YugabyteDB. The primary differentiator is MySQL compatibility: TiDB supports the MySQL wire protocol and SQL dialect, while CockroachDB is PostgreSQL-compatible and YugabyteDB offers full PostgreSQL compatibility. For teams with existing MySQL applications or expertise, TiDB provides the smoothest migration path. Performance-wise, TiDB leads on raw throughput in OLTP mixed workloads (52K TPS vs. 45K for CockroachDB and 48K for YugabyteDB) and is the clear winner for real-time analytics due to TiFlash. However, CockroachDB offers a simpler operational model with its tightly coupled architecture (no separate compute/storage components), while YugabyteDB provides the deepest PostgreSQL compatibility (it is essentially a modified PostgreSQL backend). TiDB's architecture introduces operational complexity: administrators must manage two distinct services (TiDB servers and TiKV/TiFlash nodes) instead of one. The database also uses range-based sharding (called "regions") that can become unbalanced under certain access patterns, requiring manual intervention or placement rule tuning. In geo-distributed deployments, TiDB's P99 write latency (30-80ms) is lower than CockroachDB's (50-100ms) but still significantly higher than a single-region deployment, which may be a concern for latency-sensitive applications.

The honest trade-offs are clear. TiDB's layered architecture gives it flexibility and HTAP capability but at the cost of operational complexity. The MySQL compatibility is a double-edged sword: it eases migration but means TiDB inherits some MySQL limitations, such as less sophisticated query optimizer statistics compared to PostgreSQL-based systems. The free Starter tier is generous for evaluation but severely limited for production use (25 GiB storage, no multi-region, no backups). For small deployments (under a few hundred GB), TiDB is overkill — a single-node MySQL or PostgreSQL instance will be simpler and cheaper. The database also has a steeper learning curve for operators unfamiliar with distributed systems, particularly around placement rules, region management, and TiFlash configuration. On the positive side, TiDB's HTAP capability is genuinely unique among distributed SQL databases, and its throughput numbers are competitive or better than alternatives in most benchmarks. Organizations that need to scale MySQL workloads horizontally while adding real-time analytics without a separate system will find TiDB compelling, but they must accept the operational overhead and higher cost at smaller scales.

Free Starter tier ($0/month, 25 GiB row + 25 GiB column + 2 vCPU). Dedicated tier: per-minute billing for compute nodes, starting at $0.4416/hour for 4 vCPU TiDB node (us-west-2, AWS). TiKV nodes from $0.4416/hour (4 vCPU) to $3.5328/hour (32 vCPU).

TiFlash nodes from $1.3708/hour (8 vCPU) to $4.6368/hour (32 vCPU). TiProxy small $0.1955/hour, large $0.7820/hour. Prices vary by cloud provider and region.