3 ms·
I wish we generally used solutions like this instead of always reaching for the 200lb database hammer. however, I think the article would benefit from distingu
by convolvatron 2y ago
I wish we generally used solutions like this instead of always reaching for the 200lb database hammer.
however, I think the article would benefit from distinguishing this approach from a 'real' database. that is MVCC gets you a lot more concurrency because it spreads out the exclusionary state in both time and space.
the optimistic concurrency used in the article works well at low contention and then becomes arbitrarily latent as more and more proposers try to jump into same RTT gap with both their initial attempt and their retries.
- eatonphil 2y ago> however, I think the article would benefit from distinguishing this approach from a 'real' database. that is MVCC gets you a lot more concurrency because it spreads out the exclusionary state in both time and space. I thought I already was going to be seen as being unfairly critical of the course-ness of the concurrency control.
- convolvatron 2y agoin any case thanks for writing it up. I was just thinking about doing this in a broadcast domain to provide the same kind of low-throughput bootstrapping consistency that people would normally use zookeeper or etcd for. its certainly very useful in the cases where it fits.