4 ms·
Then you are just forcing your application to deal with the dangling reference in the case of a failed "transaction". The whole point of TPC is not to have to d
by aaronbwebber 8y ago
Then you are just forcing your application to deal with the dangling reference in the case of a failed "transaction". The whole point of TPC is not to have to deal with that complexity.
Whether that complexity is actually difficult to deal with is a whole other question, I could easily believe that for some applications it's not but apparently for Dropbox it's worth implementing TPC to avoid dealing with it.
- amenghra 8y agoYes and no. You end up with a weaker api, eg you can’t perform atomic updates across shards. But you can create data atomically, perhaps build atomic counters, etc. Giving up some flexibility in the types of atomic operations you can do for a simpler architecture is sometimes worth it.
- heavenlyblue 8y agoThis also does not work well when two different processes try to do the modification at the same time. Or otherwise this does not work for entities that will be changed.