Creating an order may involve the order, items, stock and payment record.
If step four fails, should steps one to three remain?
That is what a transaction answers.
Keep related database changes atomic and keep transactions short.
Do not hold database locks while waiting for an email service or payment gateway. Commit the data and move external work to an outbox or queue.
Transactions protect database consistency. They do not magically include external systems.
Which workflow in your application requires a transaction?
<img src="https://media.daily.dev/image/upload/s--atybh-6G--/f_auto/v1786000335/ugc/content_32f7d03f-66b5-470c-80bf-85cc716cb133?_a=BAMAMicg0" alt="nest10.png">
#NestJS #DatabaseTransactions #BackendEngineering

Welcome to the NestJS Developers Hub, a collaborative community for developers passionate about NestJS! Whether you're a seasoned expert or just getting started, this group is dedicated to sharing knowledge, solving problems, and advancing our skills

Nestjs Developers

Database transactions ensure atomicity across related operations like creating an order with items, stock updates, and payment records. If any step fails, all changes should roll back. Key advice: keep transactions short, avoid holding database locks while waiting on external services like email or payment gateways, and offload external work to an outbox or queue instead.

Day 10/30 — Transactions Save Data

The outbox gets my vote. Network calls have no business holding database locks.

Man can i steal some of your images they are fire

How do you handle transactions between services?
It’s a nice topic to discuss of using transactions in different architectures