Softwr

Databases · head to head

Apache Doris vs Vitess

Apache Doris logo

Apache Doris

Databases

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

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: Apache Doris two competing commercial vendors, VeloDB and SelectDB, were founded by overlapping core contributors, which makes the long-term governance and roadmap of the project harder to predict than a single-sponsor project.; Vitess vTGate scatter queries without sharding key incur significant performance penalties
  • They diverge on capability: Apache Doris covers MySQL wire protocol, Vitess covers Horizontal Sharding.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Apache Doris and Vitess actually diverge.

Attributes where Apache Doris and Vitess differ
AttributeApache DorisVitess
Pricing modelOpen source, no licence feeUnknown
PlatformsLinux, Docker, KubernetesLinux, macOS, Docker, Kubernetes
FoundedUnknown2010

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 Apache Doris

  • MySQL wire protocol
  • Aggregate and unique key models
  • Materialised views
  • Multi-catalogue federation
  • Routine load from Kafka
  • Compute storage separation
  • Inverted indexes
  • Workload groups

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.

Apache Doris

  • A team whose MySQL read replica can no longer serve reporting queries and wants an OLAP engine its existing drivers already speaknot Vitess
  • A real-time dashboard backend needing sub-second aggregation over billions of rows with hundreds of concurrent usersnot Vitess
  • An ad or ecommerce platform that needs updates and deletes on analytical tables, which append-only OLAP engines handle badlynot Vitess
  • A data team that wants one SQL endpoint over both internal tables and existing Hive or Iceberg tables in the lakenot Vitess

Vitess

  • Transaction processingnot Apache Doris
  • Data storagenot Apache Doris
  • Application backendnot Apache Doris
  • Reportingnot Apache Doris
  • Data analyticsnot Apache Doris

Where each one falls short

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

Apache Doris

  • Two competing commercial vendors, VeloDB and SelectDB, were founded by overlapping core contributors, which makes the long-term governance and roadmap of the project harder to predict than a single-sponsor project.
  • A large share of design discussion, issue reports and documentation detail originates in Chinese, so teams that do not read it get a thinner picture of known problems and workarounds.
  • Operating a cluster means managing frontend and backend node roles, tablet balancing and compaction tuning, and compaction backlogs under heavy upsert load are a recurring production complaint.
  • The MySQL protocol compatibility is at the wire level, not full MySQL semantics, so queries and functions still need porting and the familiarity can mislead.
  • Managed cloud availability outside China and major clouds is limited compared with ClickHouse or Snowflake, so many Western adopters end up self-hosting whether they wanted to or not.

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

Apache Doris

Free
  • Apache DorisFree
    • Apache 2.0 licence with no usage restrictions
    • All engine features included
    • Community support via mailing list and Slack

Vitess

Free

No published plan breakdown. See the Vitess review.

Which should you pick?

Choose Apache Doris if

  • You need mysql wire protocol.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes.
  • You also want aggregate and unique key models.
Apache Doris 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 Apache Doris or Vitess better?
Neither clearly leads. Apache Doris 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, Apache Doris or Vitess?
Apache Doris starts at Free and Vitess at Free.
Does Apache Doris or Vitess run on more platforms?
Apache Doris runs on Linux, Docker, Kubernetes. Vitess runs on Linux, macOS, Docker, Kubernetes.
Can I use Apache Doris for free?
Both have a free tier, so you can try either at no cost before committing.
What is Apache Doris best used for?
Apache Doris is most often used for a team whose mysql read replica can no longer serve reporting queries and wants an olap engine its existing drivers already speak, a real-time dashboard backend needing sub-second aggregation over billions of rows with hundreds of concurrent users, an ad or ecommerce platform that needs updates and deletes on analytical tables, which append-only olap engines handle badly, a data team that wants one sql endpoint over both internal tables and existing hive or iceberg tables in the lake. Of those, a team whose mysql read replica can no longer serve reporting queries and wants an olap engine its existing drivers already speak and a real-time dashboard backend needing sub-second aggregation over billions of rows with hundreds of concurrent users are not what Vitess is typically brought in for.
What can Apache Doris do that Vitess cannot?
Apache Doris covers MySQL wire protocol, Aggregate and unique key models, Materialised views, Multi-catalogue federation. Vitess covers Horizontal Sharding, Connection Pooling, Query Routing, Online Schema Changes.

Answered from the vendors’ own pages

Apache Doris: Is Apache Doris really free?

Yes, it is Apache 2.0 with no usage restrictions. The commercial products are managed services from VeloDB and SelectDB.

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
Apache Doris: Can I use my MySQL tools with it?

Yes, it implements the MySQL wire protocol, so clients and BI connectors attach without a new driver, though SQL semantics differ.

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
Apache Doris: How does it compare with ClickHouse?

Doris handles updates and high concurrency more comfortably; ClickHouse is generally faster on raw single-query scan throughput and has far wider Western support.

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
Apache Doris: Who maintains it?

The Apache Software Foundation project, with most committers employed by VeloDB or SelectDB.

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
Share

Related pages

More on Apache Doris

More on Vitess

Keep looking

Other head to heads