How m10maeda/itddd works
Main components
a. Frontend: apps/web (Next.js)
b. Backend services (NestJS):
• Circles service (apps/circles)
• Profiles service (apps/profiles)
c. Shared packages (code generators, ESLint/TS configs)
d. CI/CD & orchestration: .circleci config, docker-compose
Relationships & data flows
• User ↔ Web UI (HTTP in browser)
• Web UI → Data‐access layer → API clients (generated by circles-api / profiles-api)
• API clients → REST endpoints on Circles service and Profiles service
• Each service → Domain layer → Application layer (Use Cases) → Infrastructure layer (in‐memory persistence, event‐bus, messenger)
• Domain events published internally → event‐bus → subscribers or external messenger
• Docker Compose wires together web (port 3000), circles (e.g. 3001), profiles (e.g. 3002)
Architectural patterns
• DDD layering in each NestJS service:
– Presentation (Controllers, DTOs)
– Application (Interactors / Use Cases)
– Domain (Entities, Value Objects, Policies, Repositories)
– Infrastructure (in‐memory stores, event‐bus, messenger modules)
• Monorepo with Turborepo + PNPM workspaces
• Code‐generation packages to produce type‐safe API clients
• In‐memory event sourcing for demos
Essential details checklist
[ ] Layer labels (Presentation, Application, Domain, Infrastructure)
[ ] CI/CD process at top/bottom to show build/test pipeline