Softwr

Databases · head to head

TiDB vs Vitess

TiDB logo

TiDB

Databases

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

From
Free
Rated
-
Full reviewWebsite
Vitess logo

Vitess

Databases

Scalable database clustering system for horizontal scaling of MySQL

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; Vitess vTGate scatter queries without sharding key incur significant performance penalties
  • They diverge on capability: TiDB covers MySQL wire compatibility, Vitess covers Horizontal Sharding.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which TiDB and Vitess actually diverge.

Attributes where TiDB and Vitess differ
AttributeTiDBVitess
Pricing modelfreemiumUnknown
PlatformsCloud, AWS, Azure, Google Cloud Platform, Self-managedLinux, macOS, Docker, Kubernetes
Founded20152010

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Databases).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in TiDB

  • MySQL wire compatibility
  • Horizontal write scaling
  • Distributed ACID transactions
  • TiFlash columnar replica
  • Automatic rebalancing
  • Raft replication
  • Apache 2.0 licence
  • Online schema change

Only in Vitess

  • Horizontal Sharding
  • Connection Pooling
  • Query Routing
  • Online Schema Changes
  • Shard Management
  • Replication Management
  • Automated Failover
  • MySQL

What people use each for

The jobs each tool is most often brought in to do.

TiDB

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

Vitess

  • Transaction processingnot TiDB
  • Data storagenot TiDB
  • Application backendnot TiDB
  • Reportingnot TiDB
  • Data analyticsnot TiDB

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

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.

Vitess

  • VTGate scatter queries without sharding key incur significant performance penalties
  • Foreign key constraints not enforced across shards, requiring application-level integrity handling
  • Single primary per keyspace limits multi-region write capabilities
  • Distributed transactions without proper sharding key routing suffer performance degradation

Pricing, plan by plan

TiDB

Free
  • ServerlessFree
    • 5GB storage
    • 50M request units
    • Free forever tier
  • Dedicated$250/month
    • Dedicated resources
    • SLA guarantees
    • Enterprise support

Vitess

Free

No published plan breakdown. See the Vitess review.

Which should you pick?

Choose TiDB if

  • You need mysql wire compatibility.
  • You want to start without paying.
  • You work on Cloud, AWS, Azure, Google Cloud Platform, Self-managed.
  • You also want horizontal write scaling.
TiDB review

Choose Vitess if

  • You need horizontal sharding.
  • You want to start without paying.
  • You work on Linux, macOS, Docker, Kubernetes.
  • You also want connection pooling.
Vitess review

Questions people ask

Is TiDB or Vitess better?
Neither clearly leads. TiDB starts at Free and Vitess at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, TiDB or Vitess?
TiDB starts at Free and Vitess at Free.
Does TiDB or Vitess run on more platforms?
TiDB runs on Cloud, AWS, Azure, Google Cloud Platform, Self-managed. Vitess runs on Linux, macOS, Docker, Kubernetes.
Can I use TiDB for free?
Both have a free tier, so you can try either at no cost before committing.
What is TiDB best used for?
TiDB is most often used 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. Of those, a mysql workload that has hit the write ceiling of a single primary and would otherwise need an application-level sharding layer and reporting that must run against current transactional data, where the columnar replica removes the delay and the cost of an etl pipeline are not what Vitess is typically brought in for.
What can TiDB do that Vitess cannot?
TiDB covers MySQL wire compatibility, Horizontal write scaling, Distributed ACID transactions, TiFlash columnar replica. Vitess covers Horizontal Sharding, Connection Pooling, Query Routing, Online Schema Changes.

Answered from the vendors’ own pages

TiDB: 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.

Vitess: Is Vitess free to use?

Yes. Vitess is completely free and open source under the Apache 2.0 license. It is a graduated CNCF project with no licensing costs or pricing tiers.

Source
TiDB: 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.

Vitess: What databases does Vitess support?

Vitess supports MySQL and MariaDB as backend databases. It acts as a middleware layer that adds sharding and orchestration capabilities on top of these databases.

Source
TiDB: 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.

Vitess: Does Vitess require Kubernetes to run?

No. Vitess can run on Kubernetes using the Vitess Operator, but it can also be deployed on traditional infrastructure. Kubernetes integration is optional and provides additional automation benefits.

Source
TiDB: 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.

Vitess: How does Vitess handle cross-shard transactions?

Vitess supports distributed transactions across shards, but they require queries to be routed through the sharding key. Transactions without a proper sharding key can result in slower performance.

Source
TiDB: 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.

Vitess: Does Vitess enforce foreign key constraints?

Vitess does not enforce foreign key constraints across shards by default. Referential integrity must be managed at the application layer, though per-database support can be enabled with limitations.

Source
Share

Related pages

More on TiDB

More on Vitess

Keep looking

Other head to heads