README.md

Backend

This section defines how the backend is organized using Domain-Driven Design (DDD) layered architecture.

Documents

• domain.md — entities, value objects, aggregates, domain services, and domain events.
• application.md — use cases, application services, transactions, and DTOs.
• infrastructure.md — persistence, external services, messaging, and configuration.
• interfaces.md — HTTP/CLI/event adapters, controllers, and input validation.
• api-conventions.md — response format, error codes, and versioning.
• database.md — database, migrations, and ID strategy.
• logging.md — logging, tracing, and masking.

Quick start

1. Read domain.md to understand where business rules live.
2. Read application.md before adding a new use case.
3. Read interfaces.md before adding a controller or handler.
4. Read api-conventions.md before designing an endpoint.

Core principle

Business rules are isolated in the domain layer. All other layers depend on domain through abstractions. Infrastructure implements those abstractions. Interfaces adapt the application to the outside world.