sougou

9 ms·

31.
by sougou 9y ago
Vitess has applied to join the CNCF. I recently made a presentation to the Storage Working Group: https://docs.google.com/presentation/d/1xgDO8zr3Tmic4NV9DOp_...
32.
by sougou 10y ago
Right. Vitess was built by YouTube to solve its own scalability problems. It provides sharding and cluster-management functionality. In a way, it's orthogonal. We've talked about the possibility of making Vitess work on top of Clo
33.
by sougou 10y ago
You also have the option of using local storage and combine it with a consensus protocol to keep the data distributed. You can actually achieve better durability than mainframes. Spanner uses cross-datacenter Paxos. Your data won't be
34.
MySQL Sharding Models for SaaS Applications(percona.com)
2 points by sougou 10y ago|0 comments
35.
by sougou 10y ago
Hi, thanks for the compliments :). MySQL group replication has some issues: It can fail your commits if multiple masters have conflicting transactions, which is a problem for cross-shard distributed transactions. Additionally, group replica
36.
by sougou 10y ago
Disclaimer: I work on Vitess. I'm actually a fan of TiDB and Cockroach. I've met engineers from both, and they're super-sharp. I am biased towards something like Vitess that builds on top of existing tech. The main advantage
37.
by sougou 10y ago
I'm the author of the blog. Thanks for the posts and interest shown. This proposal is a generalization of the core Paxos algorithm. It's therefore orthogonal to all customizations and adaptations. I believe that they can all benef