The original title is "The Unit of Work Boundary in PHP: One Transaction Per Use Case"

Short summary

Transaction boundaries in PHP applications should wrap entire use cases, not individual repository saves. The article explains how to centralize Doctrine's flush/commit logic in a TransactionManager interface, preventing half-committed aggregates where headers commit but items fail. This keeps domain logic free of framework concerns and ensures atomic operations at the application layer.

• •One transaction per use case prevents partial commits and data inconsistency
• •Move flush/commit logic to infrastructure layer, away from domain code
• •Use decorator pattern to wrap use cases with transaction boundaries cleanly

Generated with AI, which can make mistakes.