implement transaction management

[admiradordedamas]

Clean Architecture has a single rule: dependencies must always point toward the domain.

Many NestJS projects violate this rule, even those that claim to use Clean Architecture.

NestJS has a key feature that is often misused and ends up breaking the dependency rule.

That same feature, when used correctly (as shown in the documentation), allows the rule to be respected without hacks.

The key is to properly understand the rule and know what to do and what not to do. The documentation explains how to apply the correct option.

---

There are four strategies to implement transaction management in a NestJS project that uses Clean Architecture.

One of these strategies relies on a feature that has existed since Node.js 12.

Each strategy can be analyzed in terms of:

• Whether it violates Clean Architecture
• Whether it is coupled to the framework or a specific library
• The complexity of the required changes
• Whether it facilitates testing or not
• Whether it is thread-safe

[ayocodingit]

Excellent points. I completely agree that managing transactions without leaking infrastructure details into the domain is a major challenge in NestJS.

Using Async Local Storage (ALS) (the Node.js 12 feature you mentioned) seems to be the most 'clean' way to handle this. It allows the Use Case to define the transaction boundary (Unit of Work) while the Repositories automatically pick up the transaction context without needing to pass an EntityManager or Client as an explicit parameter. This keeps the Domain layer completely agnostic of the underlying database library.

please to review again major changes 🙏
af346bd