Softwr

Database & Data Management · head to head

Vitess vs TiDB

Vitess logo

Vitess

Database & Data Management

Scalable database clustering system for horizontal scaling of MySQL

From
Free
Rated
-
Full reviewWebsite
TiDB logo

TiDB

Database & Data Management

Open source distributed HTAP database for elastic scale and real-time analytics

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Vitess vTGate scatter queries without sharding key incur significant performance penalties; TiDB not 100% MySQL-compatible, requiring verification before migration
  • They diverge on capability: Vitess covers Horizontal Sharding, TiDB covers MySQL Compatible.

Where they differ

Only the attributes on which Vitess and TiDB actually diverge.

Attributes where Vitess and TiDB differ
AttributeVitessTiDB
Pricing modelUnknownfreemium
PlatformsLinux, macOS, Docker, KubernetesCloud, AWS, Azure, Google Cloud Platform, Self-managed
Founded20102015

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

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 Vitess

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

Only in TiDB

  • MySQL Compatible
  • HTAP Workloads
  • Horizontal Scaling
  • Strong Consistency
  • High Availability
  • Real-time Analytics
  • Elastic Scaling
  • Spark

Both cover

  • MySQL
  • Prometheus
  • Grafana
  • Linux support
  • Kubernetes support
  • Docker support

What people use each for

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

Vitess

  • Transaction processing
  • Data storage
  • Application backend
  • Reporting
  • Data analytics

TiDB

  • 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.

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

TiDB

  • Not 100% MySQL-compatible, requiring verification before migration

Pricing, plan by plan

Vitess

Free

No published plan breakdown. See the Vitess review.

TiDB

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

Which should you pick?

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

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

Questions people ask

Is Vitess or TiDB better?
Neither clearly leads. Vitess starts at Free and TiDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Vitess or TiDB?
Vitess starts at Free and TiDB at Free.
Does Vitess or TiDB run on more platforms?
Vitess runs on Linux, macOS, Docker, Kubernetes. TiDB runs on Cloud, AWS, Azure, Google Cloud Platform, Self-managed.
Can I use Vitess for free?
Both have a free tier, so you can try either at no cost before committing.
What is Vitess best used for?
Vitess is most often used for transaction processing, data storage, application backend, reporting.
What can Vitess do that TiDB cannot?
Vitess covers Horizontal Sharding, Connection Pooling, Query Routing, Online Schema Changes. TiDB covers MySQL Compatible, HTAP Workloads, Horizontal Scaling, Strong Consistency. Both handle MySQL, Prometheus, Grafana, Linux support.

Answered from the vendors’ own pages

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

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

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

Source
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
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
ShareXLinkedInRedditWhatsAppEmail

Related pages

More on Vitess

More on TiDB

Keep looking

Other head to heads