Softwr
TiDB logo

TiDB

Apache 2.0 distributed SQL database with MySQL wire compatibility and a separate columnar replica for analytical queries.

As of 30 August 2026, TiDB is free to use. TiDB scales MySQL-compatible OLTP horizontally by separating a stateless SQL layer from a distributed key-value store, and adds a columnar replica so analytical queries do not fight transactional ones. Softwr lists it under Databases. TiDB is made by PingCAP, launched in 2015, available on Web.

Overview

What TiDB does

TiDB is a distributed SQL database from PingCAP, licensed Apache 2.0. It is built from separate components: TiDB, a stateless SQL layer that speaks the MySQL wire protocol; TiKV, a distributed transactional key-value store that shards data into ranges replicated by Raft; PD, the placement driver that tracks region metadata, rebalances data and issues the timestamps that order transactions; and TiFlash, an optional columnar replica kept in sync through Raft learners. Applications connect with an ordinary MySQL driver. Because the columnar copy is maintained by the same replication mechanism as the row store, analytical queries can be routed to it without an ETL pipeline or a separate warehouse, which is what the hybrid transactional and analytical claim rests on. TiDB Cloud offers managed deployments, and more recent releases add vector search alongside the relational engine. The distinguishing property is that it scales writes horizontally while remaining something an application already speaks to. MySQL scales reads with replicas easily and writes only by sharding, which pushes routing, cross-shard queries and resharding into the application; TiDB moves that into the database and keeps ACID transactions across the whole cluster. Commercially, that is the difference between a sharding project and a migration, and it is why TiDB shows up in companies that hit the write ceiling of a single MySQL primary and do not want to write a sharding layer. The Apache 2.0 licence matters too, because in a market where several distributed databases moved to source-available terms, TiDB and TiKV, which is a CNCF graduated project, stayed permissive. The buyers are teams with a large MySQL workload that has outgrown vertical scaling, and teams that need fresh analytical queries over transactional data without a pipeline. The trade-off is footprint and latency. A credible production cluster is several PD, TiKV and TiDB nodes rather than a database server, which means it is never the cheap option at small scale; and every transaction pays for distributed consensus and a timestamp from PD, so a simple primary-key lookup that MySQL answers in well under a millisecond is measurably slower here. You buy horizontal scale by giving up the latency floor and the small footprint.

What people use it for

  • A MySQL workload that has hit the write ceiling of a single primary and would otherwise need an application-level sharding layer
  • Reporting that must run against current transactional data, where the columnar replica removes the delay and the cost of an ETL pipeline
  • Multi-region deployments needing a single logical database with automatic failover rather than manual primary promotion
  • Migrating off a sharded MySQL estate where the sharding logic in the application has become the main source of bugs and operational toil

The honest half

Where it falls short

Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about TiDB.

  • A production cluster needs several placement driver, storage and SQL nodes before it is fault tolerant, so the minimum viable footprint is far larger than a MySQL server and TiDB is never the economical choice for a small database.
  • Every transaction takes a timestamp from the placement driver and crosses the network to storage nodes, so simple point queries are slower than on single-node MySQL and latency-sensitive paths need to be measured, not assumed.
  • MySQL compatibility is at the wire and dialect level but not complete; stored procedures, triggers and events are not supported, so an application that pushed logic into the database cannot simply be repointed.
  • The columnar replica is an extra full copy of the data on its own nodes, so hybrid analytics roughly doubles storage and adds hardware that must be sized and paid for separately.
  • Operating it well requires cluster-specific expertise in TiUP or the Kubernetes operator, region hot spots, and rebalancing behaviour, so the licence is free but the running cost includes an engineer who understands distributed storage.

Cross-shopped

What people choose instead of TiDB

Each pairing was judged by two reviewers asking whether a buyer would genuinely weigh the two against each other. The ones that failed were deleted rather than published.

  • TiDB logo
    TiDB
    vs
    Cockroach Labs logo
    Cockroach Labs

    Cockroach Labs: Distributed SQL with Postgres compatibility and multi-region-first architecture for cloud-native applications

  • TiDB logo
    TiDB
    vs
    Vitess logo
    Vitess

    Vitess: MySQL sharding middleware for teams that want full control over data partitioning strategy

Pricing

What TiDB costs

Taken from the vendor's own pricing page. Prices move, so check before you buy.

Serverless

Free

  • 5GB storage
  • 50M request units
  • Free forever tier

Dedicated

$250 /mo

  • Dedicated resources
  • SLA guarantees
  • Enterprise support

Capabilities

Features

  • MySQL wire compatibility

    Existing MySQL drivers, ORMs and clients connect without change

  • Horizontal write scaling

    Data is split into ranges spread across TiKV nodes, so write capacity grows by adding nodes

  • Distributed ACID transactions

    Cross-node transactions with snapshot isolation, ordered by timestamps from the placement driver

  • TiFlash columnar replica

    A column-oriented copy maintained by the same replication path, used for analytical queries

  • Automatic rebalancing

    The placement driver moves and splits ranges as data and load change, without manual resharding

  • Raft replication

    Each range is replicated across nodes and failover happens without operator intervention

  • Apache 2.0 licence

    Permissive open source for both TiDB and TiKV, with TiKV a graduated CNCF project

  • Online schema change

    DDL applied without locking the table for the duration of the change

  • Change data capture

    TiCDC streams changes out to downstream systems for replication or integration

  • Managed cloud

    TiDB Cloud provides hosted clusters, including a serverless-style entry tier

Answered, with sources

Questions people ask

Each answer names the page it came from, so you can check it rather than take our word for it.

Is TiDB a drop-in replacement for MySQL?

At the protocol and dialect level it is close, and most applications connect unchanged. Stored procedures, triggers and events are not supported, and latency characteristics differ, so it needs testing rather than assumption.

What licence is it under?

Apache 2.0, for both TiDB and the underlying TiKV storage engine. TiKV is a graduated CNCF project, which is a meaningful governance signal in a market where several competitors moved to source-available licences.

Do I need TiFlash?

Only for analytical queries. It is an optional columnar replica; without it TiDB is a distributed transactional database. With it you get analytics on live data at the cost of an additional full copy.

Is the managed cloud the same software?

TiDB Cloud runs the same engine, with the control plane, scaling and operational tooling provided as a service. The entry tier is metered differently from a dedicated cluster, so the cost model rather than the engine is what changes.

When is TiDB the wrong choice?

When the database is small enough for one server, when latency on single-row lookups is the primary constraint, or when the application depends on MySQL stored procedures and triggers.

Behind it

Who makes TiDB

Company
PingCAP
Based in
San Mateo, California
Founders
Liu Qi, Huang Dongxu, Cui Qiu

Timeline

TiDB over time

  1. Funding2021-05-01$300m

    Series D funding of $300M led by GGV and Coatue for R&D and market expansion

    Source
  2. Founded2015-04-01

    PingCAP founded to solve the database scaling nightmare by building distributed SQL inspired by Google Spanner

    Source
Share

Keep looking

Where to go from TiDB

Best Databases software for

Compare TiDB with

Other Databases software

  • The cloud-native distributed SQL database

    Free plan14 researched notes
  • Scalable database clustering system for horizontal scaling of MySQL

    Free plan12 researched notes
  • The heart of the Elastic Stack for search and analytics

    Free, then $16.4/mo11 researched notes
  • The real-time distributed SQL database for data-intensive applications

    Free, then $0.99/mo14 researched notes
  • Google Cloud's serverless analytical warehouse, billed either by bytes scanned per query or by reserved compute slots.

    Free plan13 researched notes
  • MIT-licensed analytical SQL database that runs inside your process, with no server, no dependencies and one writer at a time.

    Free plan14 researched notes
  • Fast, scalable cloud data warehouse from AWS

    Free plan12 researched notes
  • Fast open-source column-oriented database for real-time analytics

    Free plan12 researched notes
  • Real-time analytics database for sub-second OLAP queries

    Free plan10 researched notes
  • The modern database for enterprise applications

    Free plan12 researched notes
  • The open source relational database for the enterprise

    Free plan16 researched notes
  • Time-series database built on PostgreSQL for real-time analytics

    Free plan12 researched notes
  • Kafka-compatible streaming platform with no ZooKeeper or JVM

    Free plan9 researched notes
  • Streaming database that maintains incremental materialised views in SQL instead of Flink jobs

    Free, then $0.227/hour12 researched notes
  • The real-time big data database compatible with Cassandra

    Free plan11 researched notes
  • Multi-protocol event broker sold as software, cloud service or a hardware appliance

    Free plan12 researched notes
  • Small, fast, self-contained SQL database engine

    Free plan10 researched notes
  • Apache 2.0 MPP analytical database built for joins on open table formats

    Open source12 researched notes

Softwr does not host reviews and shows no star rating for TiDB, because a rating we did not collect is not ours to publish. What is here is the pricing and platform detail from the vendor’s own pages, limitations we could state concretely, and alternatives a reviewer confirmed people weigh against it. Tell us if any of it is wrong.

More on TiDB

Best Databases software alternatives

Industrial process historian with published per-tag pricing and no client licence fees

Per tag band per year

NetApp-owned managed service for Cassandra, Kafka, OpenSearch, PostgreSQL and Cadence with a bring-your-own-cloud model

quote

Erlang MQTT broker for large IoT fleets, relicensed to BSL with production free use limited to one node

Per month by connection and session volume

Attribute-based access control and masking applied inside Snowflake, Databricks and BigQuery

quote

MPP analytical database with a MySQL wire protocol and sub-second aggregation on wide tables

Open source, no licence fee

Streaming database that maintains incremental materialised views in SQL instead of Flink jobs

Per RisingWave Unit hour

Centralised data access governance from the creators of Apache Ranger, now rebranding as Trust3 AI

quote

The Meta-lineage distributed SQL query engine, distinct from the Trino fork

Open source, no licence fee

Compare TiDB with alternatives