domain-decomposition-api-design-advisor

To define bounded contexts, break the feature into use cases, identify core nouns and aggregates, and separate commands from queries. This decomposition workflow clarifies domain boundaries and ownership while reducing system coupling.

Design API contracts by explicitly specifying idempotency, versioning, error semantics, and data ownership before implementation begins. This discipline ensures explicit technical boundaries that survive system redesigns and future changes.

Choose a modular monolith or bounded context inside it when boundaries are unclear, optimizing for clear ownership and explicit invariants. This approach avoids premature microservice enthusiasm and prevents shared databases as a default pattern.

Capture architecture decisions using ADR-style reasoning to document options, rationale, and follow-up risks. This approach ensures decision traceability and guides system evolution across multiple teams with clear ownership.

Convert vague product concepts into explicit technical boundaries by identifying use cases and core nouns, then defining bounded contexts and API contracts. This workflow ensures boundary definition and compatibility planning for feature scoping.