vitessio

Vitess: Scale MySQL Horizontally with Sharding

Vitess is a cloud-native distributed database system built around MySQL. It uses generalized sharding to scale data across database servers while keeping application code and queries independent of how data is distributed.

Stars
21.4k
Forks
2.4k
Stars, last 30 days
+39
Last commit
today
Contributors
100+

Our take

Activeregular commits and releases

Health score

69/100

How it is scored
Activity
78
Community
93
Issues
58
Pull requests
47

+39 stars in the last 30 days

  • More contributors than 78% of the projects we track

Vitess is an actively maintained, mature option for teams that need sharded MySQL and can take on the operational requirements of a distributed database system.

Good fit if

  • You need to scale a MySQL-backed service across database servers using sharding.
  • Your team can run a cloud-native system and meet its Go and Docker requirements.
  • You want a project with regular commits and releases, a broad contributor base, and an Apache-2.0 license.

Look elsewhere if

  • Your application does not need MySQL sharding or horizontal database scaling.
  • You need a solution that avoids the operational complexity of distributing and managing database shards.
  • Your environment cannot support the project's Go and Docker requirements.
All health signals
Last commit2026-11-13 (today)
Commits, last 90 days100+
Releases, last 12 months17 (latest v24.0.5, 2026-10-13)
Contributors100+ (top contributor: 15% of commits)
Issues closed, last 90 days5+ (typically closed in 3 days)
Pull requests merged, last 90 days49 (typically merged in 2 days)
Project age13 years

Checked on 2026-11-14 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

21,426

Forks

2,448

Change since Nov 17, 2026: +4 stars·+3 forks

Overview

Vitess is a cloud-native distributed database system built around MySQL. It addresses the challenge of scaling a MySQL-backed application across multiple database servers by using generalized sharding, while keeping application code and queries agnostic to where data resides.

Teams can split or merge shards as their needs change, with an atomic cutover. Vitess is intended for applications that need to grow beyond a single MySQL server and are prepared to operate a distributed database layer.

Key Features

  • Distributes MySQL data across shards for horizontal scaling.
  • Keeps application code and database queries independent of data placement.
  • Supports splitting and merging shards as scaling needs change.
  • Provides an atomic cutover when changing shard layouts.
  • Offers a Kubernetes-oriented, cloud-native deployment model.

Use Cases

  • A database team scaling a growing MySQL application beyond the capacity of one server.
  • Platform engineers managing sharded MySQL deployments in Kubernetes.
  • Operators changing shard layouts as data and traffic grow, while limiting the disruption of cutovers.
  • Application teams that want to scale their MySQL data distribution without making each query depend on shard placement.

What you need

Detected in the repository

  • Go 1.27.4 or newer (from go.mod)
  • A Dockerfile, so it can run in a container
  • A test suite and automated checks on GitHub Actions

License in plain words

Apache-2.0permissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the license, the NOTICE file and a note of your changes
  • Share your changes: no
  • Includes an explicit patent grant from the contributors:

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Start with the Vitess README and the project documentation for setup and deployment instructions.

Alternatives

  • multigres: Multigres applies Vitess-style sharding and operations to PostgreSQL, while Vitess is built around MySQL.
ProjectLanguageLicenseStarsStatus
VitessGoApache-2.021.4kActive
multigresGoApache-2.02.7kActive

Considerations

Vitess adds a distributed sharding layer to MySQL, so adopting it means operating more than a standalone database. The project requires Go and Docker, and teams should assess how its deployment model fits their infrastructure. Development is active, with frequent commits and releases and contributions from many people; recent issue closures are limited, though the reported median time to close is short. The Apache-2.0 license permits broad use, subject to its license terms.

Found this useful?

Share it with someone who would like Vitess.

Comparisons