Atomic writes used to be one of the important reasons we stuck with relational databases. The rule was simple: either all your updates succeed, or they all fail. But as we moved to NoSQL databases in distributed systems, we often traded that safety for scale. Now, the pendulum is swinging back. Developers building microservices and server-less apps are realizing that writing manual undo logic (compensating transactions) is a nightmare, and they want their NoSQL databases to handle that heavy lifting again.
However, atomicity isn’t standard across the cloud. AWS, Azure, GCP, and Alibaba all offer transaction capabilities, but they have wildly different rules regarding locking, limits, idempotency, and consistency guarantees.
Read More from DZone.com Feed