spec:architect

Domain-driven design aligns domain language with implementation, while hexagonal architecture manages complexity by separating business rules from I/O concerns using a functional core and effectful edge.

Design new features by isolating core domain logic from external integrations, using aggregates, entities, value objects, and domain events to enforce invariants and clarify component responsibilities across bounded contexts.

The functional core and effectful edge pattern enforces separation of concerns by isolating pure domain logic from external I/O operations, utilizing dependency inversion to keep business rules independent of infrastructure.

Use domain events and bounded contexts during task decomposition to establish clear boundaries between system components, align domain language with implementation, and manage complexity across distinct business areas.

Yes, this approach clarifies component responsibilities by defining bounded contexts and applying hexagonal patterns, ensuring clear boundaries and separation of concerns across integrated business domains.

Recommended architectural patterns include dependency inversion, functional core versus IO edge separation, and bounded contexts, alongside curated DDD, data modeling, and API design references to accelerate decisions.