vitessio/vitess

Vitess is a database clustering system for horizontal scaling of MySQL.

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on March 25th, 2026
Created on June 27th, 2013
Open Issues & Pull Requests: 1,132 (+1)
GitHub issues: Enabled
Number of forks: 2,404
Total Stargazers: 21,353 (+0)
Total Subscribers: 479 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.0 hours
Mean response time: 155.0 days
90th percentile: 492.8 days
Tracked items: 1,341

How this project is maintained

About 17% of issues opened in the past year have never received a reply. 50% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "Component: General" is answered fastest, typically in under an hour, while "Component: Query Serving" waits about 4 days. 31% of tracked open issues have had no activity in three months. Only 58% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 480
New in 7 days: 20
Closed in 7 days: 8
Avg open age: 419 days
Stale 30+ days: 404
Stale 90+ days: 308

Recent activity

Opened in 7 days: 20
Closed in 7 days: 8
Comments in 7 days: 7
Events in 7 days: 67

Top labels

  • Type: Bug (820)
  • Component: Query Serving (485)
  • Type: Feature (306)
  • Component: VReplication (286)
  • Type: Enhancement (268)
  • Component: Cluster management (112)
  • Component: General (107)
  • Component: VTOrc (93)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Vitess is a database clustering system for horizontal scaling of MySQL.

Vitess solves the problem of scaling MySQL beyond the capacity of a single server by implementing a distributed database layer that abstracts away the complexity of data sharding from application code. The system allows queries and application logic to remain agnostic to how data is distributed across multiple database servers. It achieves this through generalized sharding, and supports dynamic shard management—you can split and merge shards as your application grows, with atomic cutover operations that take only seconds.

Vitess suits organizations running large MySQL deployments that need to scale horizontally without rewriting application code. It is particularly valuable for teams managing tens of thousands of database nodes or anticipating rapid growth in data volume. The project originated as YouTube's core database infrastructure and has since been adopted by other large companies. If you are evaluating sharding solutions, Vitess distinguishes itself by keeping the distribution logic transparent to applications, eliminating the need to embed sharding awareness into your codebase.

The project receives issue reports from both core maintainers and external users, indicating real-world adoption without an overwhelming support burden. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker centers on bug fixes and two main components: Query Serving and VReplication, suggesting the project's development focus remains on query routing reliability and data replication across shards.