ACID

Atomicity, Consistency, Isolation, Durability — the guarantees a relational transaction gives you.

Why we need this / what value this brings

Gives you a strong, well-understood correctness guarantee for free, as long as the operation fits in a single database transaction.

Any multi-step write that must all-or-nothing succeed (booking creation + payment hold + slot decrement).

Wrap the multi-step write in a single DB transaction; let the database handle atomicity/isolation rather than hand-rolling compensating logic.

Which Localz operations genuinely need a DB transaction (booking creation + payment hold) vs don't?

Empty folder — drop notes, links, and findings here as you research.