Vitess
No written verdict yet. Here is what commenters said.
5recommend
0warn against
Feb 9, 2026first mention
Sep 11, 2026latest mention
Why people recommend it
“as a heavy Vitess/MySQL user I do fear the split focus from PlanetScale”
heavy Vitess/MySQL useron “Neki – Sharded Postgres”
“Vitess/Neki, vector stores, spacetime are all really good things to be happening”
Show 3 more
“Vitess and Neki both let you configure this via the VSchema”
“I would encourage you to look at the code and read the documentation”
Caveats and dissent
No one in these comments warned against it.
Often compared with
Who recommends it in their own words
Threads where it came up
- Making 768 servers look like 1 4 mentions
- Zero downtime migrations at Petabyte scale 3 mentions
- Neki – Sharded Postgres 2 mentions
- Another GitHub outage in the same day 2 mentions
- 118M Queries per Second on Neki 1 mention
- Ok, but does it scale? 1 mention
Data: vitess.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 17
Not being rude, I just do not like the work of my company being written off and under appreciated with comments like yours. Saying it's an open source alternative when it is clearly not is incredibly disingenuous. Anyone can start a project and say it's an alternative until it achieves the same results is not an alternative. They have raised 10x more venture funding than my company, and we have out executed them with
“Vitess does have some options for atomic cross-shard commits”
“as a heavy Vitess/MySQL user I do fear the split focus from PlanetScale”
“Vitess/Neki, vector stores, spacetime are all really good things to be happening”
“Vitess is a database clustering system for horizontal scaling of MySQL”
“Yep! https://vitess.io/docs/reference/features/distributed-transaction/”
“Vitess and Neki both let you configure this via the VSchema”
“https://www.etsy.com/codeascraft/migrating-etsyas-database-sharding-to-vitess”
“It looks like it does support transactions, but they basically destroy the performance benefits”
“Looks like it's not drop-in, you need to heavily modify your data and indexes structurally”
“making Vitess for Postgresql”
“building an equivalent to Vitesse for Postgres”
“I would encourage you to look at the code and read the documentation”
“It's open source. If you want to understand exactly how, you certainly can! :-)”
“It's open source. You can get as many details as you like :)”
Here’s a post from 2021 about the migration! [0] I guess 2021 is a long time ago now. How did that happen… [0] https://github.blog/engineering/infrastructure/partitioning-githubs-relational-databases-scale/
“GitHub pretty famously used Vitess”