transaction-expert

What problem does it solve?

This Skill centralizes and standardizes transaction boundary management within the Application Layer, strictly separating Command (write) and Query (read) operations. It delegates transaction responsibilities from Services to dedicated Manager and Facade components, leading to cleaner, more robust, and testable business logic.

Core Features & Use Cases

• CQRS Transaction Separation: Defines TransactionManager (for single-port persistence) and ReadManager (for single-query port retrieval) for atomic operations, ensuring clear responsibilities.
• Complex Transaction Orchestration: Creates CommandFacade (combining 2+ TransactionManagers) and QueryFacade (combining 2+ ReadManagers) for orchestrating complex, multi-aggregate transactions or data compositions.
• Strict @Transactional Usage: Enforces @Transactional at the method level within Managers and Facades, prohibiting its use at the class level or within Services for precise control.
• Zero-Tolerance Rules: Prohibits @Service (uses @Component), business logic within Managers/Facades, and object creation (delegates to Factory), ensuring architectural integrity.
• Use Case: When designing a new business transaction that involves multiple aggregates or complex data retrieval, use this skill to generate the appropriate Manager or Facade. This ensures correct transaction boundaries and clean architecture, allowing you to focus on the core business problem.

Quick Start

Design a transaction boundary for a 'Place Order' use case, involving multiple persistence operations, using a CommandFacade.