software-design

Refactor code to enforce domain boundaries by guiding module organization and placing business rules on domain entities or value objects. This keeps changes local and decouples core logic from infrastructure using hexagonal architecture.

Structure code for hexagonal architecture by isolating core domain logic from infrastructure through ports and adapters. This approach enforces proper layering, ensuring business rules remain decoupled and maintainable across bounded contexts.

Domain-driven design handles SRP by enforcing one reason to change per module, improving cohesion and coupling. It guides the placement of business rules on domain entities rather than services, ensuring invariants remain consistent during refactoring.

You can use design heuristics for PR reviews in layered architecture by checking single-responsibility, boundary clarity, and domain-owned behavior. These heuristics ensure business rules are correctly placed on entities and value objects.

Avoid domain-driven design for module organization when bounded contexts are unclear or when infrastructure changes dominate business logic. Without well-defined invariants and domain entities, enforcing hexagonal architecture adds unnecessary complexity.