Atomicity (in the sense of “ACID”) states that for a series of operations performed against a database, either every one of them commits together, or they’re all rolled back; no in between states are allowed. For code that needs to be resilient to the messiness of the real world, it’s a godsend. Instead of bugs that make it to production changing data and then leaving it permanently corrupt, those
![How Postgres Makes Transactions Atomic](https://cdn-ak-scissors.b.st-hatena.com/image/square/c6dd8aa60f1f2f423ffa21a5e8faebb78c99cee3/height=288;version=1;width=512/https%3A%2F%2Fbrandur.org%2Fassets%2Fimages%2Fpostgres-atomicity%2Ftwitter%402x.jpg)