0124-architecture-patterns

What problem does it solve?

It solves tangled dependencies and hard-to-test backend code by providing proven backend architecture patterns that enforce clear boundaries between domain logic, application workflows, and infrastructure concerns.

Core Features & Use Cases

• Clean Architecture: Separate Entities (domain), Use Cases (application rules), Interface Adapters (translation), and Framework/Drivers (DB, UI, external services) with inward-only dependencies.
• Hexagonal Architecture: Model the system around ports and adapters so the domain core stays framework-free while infrastructure implementations can be swapped freely.
• Domain-Driven Design (DDD): Establish bounded contexts plus tactical modeling (entities, value objects, aggregates, repositories, domain events) to keep models coherent and resilient.
• Testing & Troubleshooting: Enable unit tests without a running database by injecting abstract ports and using in-memory adapters; resolve dependency cycles by enforcing imports that flow inward only.

Quick Start

Ask the AI to refactor your service into Clean/Hexagonal layers by defining domain entities and ports first, then building use cases, and finally wiring adapters (controllers and infrastructure) through dependency injection, while adding an in-memory test repository to keep use-case tests database-free.