3 ms·

> ● SQL query compatibility > ● Minimal changes to the application > ● Runs MySQL in backend > ● Kubernetes native > ● Provides Kubernetes opera

by alecco 4y ago

> ● SQL query compatibility > ● Minimal changes to the application > ● Runs MySQL in backend > ● Kubernetes native > ● Provides Kubernetes operator > We evaluated multiple candidates and chose Vitess https://github.com/vitessio/vitess https://github.com/vitessio/vitess But it's very light on numbers and doesn't show trade-offs or anything.

Thaxll 4y ago
Vitess was used for all of Youtube, they moved to Spanner couple of years ago, Vitess is proven and scalable tech.
tbarn 4y ago
KubeCon talks should be out in the next month or so and it has more details.
edf13 4y ago
> Vitess has been a core component of YouTube's database infrastructure since 2011, and has grown to encompass tens of thousands of MySQL nodes. Would love to hear more about this implementation
- XCSme 4y ago
  Me too, especially, what it does different from if you would manually shard/partition your database. Is it just the automated sharding?