DDD Architecture Guidance.
Apply Domain-Driven Design, Layered, Onion, Hexagonal, and CQRS correctly to business-domain backend systems with source-aware constraints.
Built for
What it does.
Guides AI agents through authoritative architecture decisions for Java, Kotlin, C#, .NET, Go, and Python business systems. Distinguishes Domain-Driven Design as a domain modeling methodology from Layered, Onion, Hexagonal/Ports and Adapters, and CQRS as separate architecture styles with their own dependency and boundary rules. Uses jMolecules as the primary Java/Kotlin reference and translates concepts idiomatically into other ecosystems.
Enforces explicit architecture constraints when a project has chosen Layered, Onion, Hexagonal, or CQRS. Does not weaken boundary rules or misattribute violations. Prioritizes foundational sources—Evans, Cockburn, Fowler, Palermo, Young—over synthesis and opinion. Treats Clean Architecture and Explicit Architecture cautiously as secondary references, not authority.
Covers bounded contexts, aggregates, entities, value objects, repositories, domain services, domain events, ports and adapters, CQRS without Event Sourcing assumptions, and architecture unit testing with ArchUnit and ArchUnitNET. Includes backend guidance for Java/Kotlin, C#/.NET, Go, and Python; conditional guidance for Dart/Flutter and Swift/iOS only when substantial domain behavior justifies it. Avoids forcing DDD or ceremony into simple CRUD.
What’s inside.
Everything you need in the bundle. No tutorials. No assembly.
- 01Source policy document that separates foundational architecture sources from implementation guidance and opinionated synthesis
- 02Architecture constraints by style (Layered, Onion, Hexagonal, CQRS) so violations are attributed correctly, not misnamed as DDD failures
- 03jMolecules-oriented Java/Kotlin examples with package boundaries, aggregates, repositories, and annotation-driven architecture expression
- 04Idiomatic examples for C#/.NET, Go, and Python that translate DDD and architecture patterns into ecosystem conventions
- 05ArchUnit and ArchUnitNET test sketches for enforcing dependency direction, boundary rules, and architectural consistency
- 06Review checklist and decision workflow to identify chosen architecture, apply its constraints, and avoid unnecessary ceremony in CRUD-heavy services
Drop it in. Press go.
- №01
Download
Buy once, get the bundle by email and on your dashboard.
- №02
Drop it in
Upload the files to your agent.
- №03
Connect
Wire up your tools with the setup notes.
- №04
Press go
The agent runs. You handle the people part.
About the creator.
Things people ask.
$9
DDD Architecture Guidance.