Vitess at YouTube: Horizontal Sharding Without Leaving MySQL
YouTube built Vitess to shard MySQL with a proxy, a lock server, and resharding workflows so a massive video site could keep SQL instead of betting the company on a new store.
Tag
5 articles · 15 min of reading
YouTube built Vitess to shard MySQL with a proxy, a lock server, and resharding workflows so a massive video site could keep SQL instead of betting the company on a new store.
VTGate, VSchema, and scatter vs targeted queries: the routing layer that made YouTube's MySQL split look like one database.
Distributed tables, reference tables, and the query router: what Citus can push down, and which joins become network products.
How Slack's original one-workspace-per-shard data model buckled under Enterprise Grid and giant workspaces, and why finer-grained sharding replaced it.
How Uber's Ringpop library used consistent hashing and a gossip protocol to shard stateful services without depending on a single coordinator.