3 ms·

Thanks -- just curious, am I correct to interpret this to basically mean that thus far, the performance of the system basically relies on users to explicitly de

Thanks -- just curious, am I correct to interpret this to basically mean that thus far, the performance of the system basically relies on users to explicitly define colos nicely within their application-level data model? For some reason this reminds me of something like the entity group concept in Google's Megastore [1]. [1] http://cidrdb.org/cidr2011/Papers/CIDR11_Paper32.pdf http://cidrdb.org/cidr2011/Papers/CIDR11_Paper32.pdf

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 writes using optimistic concurrency control that would come into play sooner. Our guidance is therefore that users try to reserve transactions for when there's correctness critical reasons why two objects need to be updated together and rely on asynchronous primitives to handle "eventually consistent" mutations.