Infrastructure Design

Practical infrastructure patterns for layered (hexagonal/DDD) applications. The domain defines business consistency requirements, the application defines unit-of-work boundaries and capability ports, and infrastructure implements transaction and delivery mechanics.

Workflow

1. Identify the concern — is this about event delivery, data consistency, read performance, or query simplification?
2. Choose the right reference — load the relevant file from references/.
3. Apply at the right layer — domain owns business meaning, application owns orchestration contracts, and infrastructure provides technical adapters.
4. Validate the tradeoff — every infrastructure decision trades something (complexity, consistency, latency). Make the tradeoff explicit.

Quick Decision Map