Where do you usually implement transaction logic in domain design?

Question

• In the consumer code? (e.g. controller)
• In the repositories?
• In the services?

Answer 1

For starters, this is a pretty moot point, so you should get a lot of different answers.

My own business is that transactions (ACIDs) are a function of certain storage mechanisms (primarily relational databases), so I’m looking at a technology-specific concept. Before anyone protests that this is only a theoretical argument, consider a few possible cases where the data store (Warehouse) will not be transactional:

• (, Amazon) . ,
• REST

, , . , , , , , .

, ( ).

---

, , , , () .