Software · head to head
TiDB vs Vitess
TiDB
Software
Open source distributed HTAP database for elastic scale and real-time analytics
- From
- Free
- Rated
- -
Vitess
Software
Scalable database clustering system for horizontal scaling of MySQL
- From
- Free
- Rated
- -
The short version
- Each has a real cost: TiDB not 100% MySQL-compatible, requiring verification before migration; Vitess vTGate scatter queries without sharding key incur significant performance penalties
- They diverge on capability: TiDB covers MySQL Compatible, Vitess covers Horizontal Sharding.
Where they differ
Only the attributes on which TiDB and Vitess actually diverge.
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Unknown).
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 Compatible
- HTAP Workloads
- Horizontal Scaling
- Strong Consistency
- High Availability
- Real-time Analytics
- Elastic Scaling
- Spark
Only in Vitess
- Horizontal Sharding
- Connection Pooling
- Query Routing
- Online Schema Changes
- Shard Management
- Replication Management
- Automated Failover
- Kubernetes
Both cover
- MySQL
- Prometheus
- Grafana
- Linux support
- Docker support
- Kubernetes support
What people use each for
The jobs each tool is most often brought in to do.
TiDB
- Transaction processing
- Data storage
- Application backend
- Reporting
- Data analytics
Vitess
- Transaction processing
- Data storage
- Application backend
- Reporting
- Data analytics
Both are used for transaction processing, data storage, application backend, reporting, data analytics, on those jobs the choice comes down to price and fit rather than capability.
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
TiDB
- Not 100% MySQL-compatible, requiring verification before migration
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
FreeNo published plan breakdown. See the Vitess review.
Which should you pick?
Choose TiDB if
- You need mysql compatible.
- You want to start without paying.
- You work on Cloud, AWS, Azure, Google Cloud Platform, Self-managed.
- You also want htap workloads.
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.
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 transaction processing, data storage, application backend, reporting.
- What can TiDB do that Vitess cannot?
- TiDB covers MySQL Compatible, HTAP Workloads, Horizontal Scaling, Strong Consistency. Vitess covers Horizontal Sharding, Connection Pooling, Query Routing, Online Schema Changes. Both handle MySQL, Prometheus, Grafana, Linux support.
Answered from the vendors’ own pages
TiDB: Is TiDB MySQL-compatible?
Yes, TiDB speaks the MySQL protocol, so existing MySQL clients, ORMs, and drivers work without modification. However, TiDB is not 100% MySQL-compatible.
SourceVitess: 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.
SourceTiDB: How does TiDB scale?
TiDB provides automatic horizontal scaling with compute and storage scaling independently. It splits compute (TiDB servers) from storage (TiKV) to allow adding nodes without data replication.
SourceVitess: 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.
SourceTiDB: Does TiDB support analytics workloads?
Yes, TiDB is an HTAP database with TiFlash columnar engine providing analytics capabilities alongside transactional processing on the same data without separate pipelines.
SourceVitess: 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.
SourceVitess: 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.
SourceVitess: 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