whichdb
vs

Espresso vs Vitess

Espresso: LinkedIn's internal, MySQL-backed distributed document store that serves as source of truth for its core data. Vitess: CNCF-graduated sharding and clustering layer that makes a fleet of MySQL servers look like one database.

key differences

  • Espresso is primarily a document database; Vitess is relational.
  • Licensing: Espresso is proprietary (Proprietary (LinkedIn internal)); Vitess is open source (permissive) (Apache License 2.0).
  • Only Espresso has streaming ingest.
  • Only Vitess has joins, materialized views, compression, role-based access.

choose espresso for

  • +Studying how a large social network built its primary document store
  • +Reference design for MySQL-backed sharded document services with CDC
  • +Background for systems such as Helix, Databus and Kafka-based CDC

best at · OLTP, Content

choose vitess for

  • +Scaling a large MySQL application beyond one primary
  • +Multi-tenant SaaS sharded by customer
  • +Consolidating many MySQL databases under one routing layer
  • +Zero-downtime schema migrations on huge tables

best at · OLTP, Metadata, Content

EspressoLinkedIn's internal, MySQL-backed distributed document store that serves as source of truth for its core data.
VitessCNCF-graduated sharding and clustering layer that makes a fleet of MySQL servers look like one database.
overview
Primary model
Document
Relational
Also supports
–
Document
Type
Research prototype
Database engine
Status
Active
Active
Developer
LinkedIn
Vitess Authors (CNCF; maintained largely by PlanetScale)
First release
2012
2012
Latest version
–
24.0.5 (Oct 13, 2026)
License
ProprietaryProprietary (LinkedIn internal)
Open source (permissive)Apache License 2.0
Free tier
—
✓
popularity
WhichDB Score
0.0
21.2
Rank
#729
#142
GitHub stars
–
21.4K
Stack Overflow questions
–
54
scale & guarantees
Comfortable data size
Massive (Multi-PB)
Massive (Multi-PB)
Horizontal scaling
Native
Native
Multi-region
Read replicas
Read replicas
ACID
Limited
Limited
Consistency
Strong, Eventual
Strong, Eventual
Schema
Flexible
Strict
Architecture
Distributed, Primary replica
Distributed, Primary replica, Client server
deployment
Self-hosted
—
✓
Vendor-managed cloud
—
—
Serverless
—
—
Embedded
—
—
Edge
—
—
Clouds
–
–
capabilities
Transactions
✓
✓
Joins
—
✓
Secondary indexes
✓
✓
Full-text search
✓
✓
Vector search
—
—
Geospatial
—
—
JSON
✓
✓
Change data capture
✓
✓
Triggers
—
—
Stored procedures
—
—
Materialized views
—
✓
TTL / expiry
—
—
Pub/Sub
—
—
Columnar storage
—
—
In-memory
—
—
Durable persistence
✓
✓
Compression
—
✓
Encryption at rest
—
—
Role-based access
—
✓
Time travel
—
—
Branching
—
—
Online schema changes
✓
✓
Streaming ingest
✓
—
Offline sync
—
—
Runs in WebAssembly
—
—
interfaces
Query languages
REST resource URIs (key and collection lookups), Secondary-index queries
SQL
Client languages
Java
Java, Go, Python, JavaScript, PHP, Ruby, C#
Best for
OLTP, Content
OLTP, Metadata, Content
Add more to this comparisonNot sure either fits? Try smart match

Espresso vs Vitess: FAQ

What is the difference between Espresso and Vitess?

Espresso: LinkedIn's internal, MySQL-backed distributed document store that serves as source of truth for its core data. Vitess: CNCF-graduated sharding and clustering layer that makes a fleet of MySQL servers look like one database. Espresso is primarily a document database; Vitess is relational. Licensing: Espresso is proprietary (Proprietary (LinkedIn internal)); Vitess is open source (permissive) (Apache License 2.0). Only Espresso has streaming ingest.

When should I choose Espresso over Vitess?

Choose Espresso for studying how a large social network built its primary document store; reference design for MySQL-backed sharded document services with CDC; and background for systems such as Helix, Databus and Kafka-based CDC. Choose Vitess for scaling a large MySQL application beyond one primary, multi-tenant SaaS sharded by customer and consolidating many MySQL databases under one routing layer.

Is Espresso or Vitess more popular?

Vitess ranks #142 on the WhichDB Score (21.2/100) and Espresso ranks #729 (0.0/100). Popularity is not fit: check the requirements that matter for your project.

Are Espresso and Vitess open source?

No. Espresso is proprietary, closed-source software. Yes. Vitess is open source. License: Apache License 2.0.