tahara

3 ms·

1. 1.▲
   by tahara 8y ago

   There is somewhere between where we are today and a completely uncollocated free-for-all where the system would fall over. There's a separate axis of the rate at which users request transactions (with locks) versus non-transactional wr
2. 2.▲
   by tahara 8y ago

   That's what we thought, too. (Un)fortunately(?) that's not the case anymore given our product offerings :)
3. 3.▲
   by tahara 8y ago

   We have a routing tier of a few hundred machines. Any of those can serve as transaction coordinator. This is one of the places where having a transaction record is useful -- in general, our locking and non-transactional read scheme will wai
4. 4.▲
   by tahara 8y ago

   Vitess is a bit less of an application abstraction layer in the sense of Edgestore, Tao, and others, and more of an operational abstraction that hides physical sharding and taking the pain out of repartitioning to accommodate new capacity.
5. 5.▲
   by tahara 8y ago

   For us (Dropbox), the threshold ended up being multiple product teams having to implement ad-hoc two-phase commit over their datatypes and burning engineer hours not to implement it but to prove that they had gotten it right and to handle t
6. 6.▲
   by tahara 8y ago

   Thanks for the references -- will take a look. Edgestore's API is set up to shepherd users into good collocation patterns by default, and a lot of work over the past year or two went into improving collocation and educating users about