I'll be interested to see the further details discussed in the isolation post, which might answer some questions. This is basically the same how the DynamoDB c

I'll be interested to see the further details discussed in the isolation post, which might answer some questions. This is basically the same how the DynamoDB client transaction library works. The two major problems with that library are: * High write amplification (7N for DDB, probably similar for CockroachDB) * Poor throughput under contention. This is mostly due to the immediately abort conflicting pending transactions policy, which could be changed if contention is frequent (client side exponential back off is probably good enough for most cases). The special sauce they didn't mention might also help here.