Atomicity means a transaction succeeds or fails as one indivisible unit: partial changes are rolled back, leaving the data as though the transaction never happened. section 8.2.1
The last pair of sneakers
A purchase must both deduct the last pair from inventory and create an order. If payment times out or power fails halfway through, atomicity rolls back the changes; the sneakers return to the shelf. section 8.2.1
Atomicity within one database does not make a database write and a network publish happen together reliably. Saving an order but losing the event can leave downstream workers unaware; publishing first can announce an order that was never saved. The Transactional Outbox Pattern is identified as a way to address this dual-write risk. section 7.5.1


















