Service Boundary Design

Core Workflow

1. Identify domains, actors, data ownership, latency needs, deployment model, team ownership, and failure tolerance.
2. Define service or module responsibilities, owned data, public interfaces, and forbidden dependencies.
3. Map synchronous calls, async events, shared storage, and integration points.
4. Evaluate coupling, transaction boundaries, consistency needs, and migration path.
5. Prefer simpler module boundaries before distributed services unless scale, ownership, isolation, or reliability needs justify separation.
6. Document tradeoffs, risks, and review triggers.

Safety Rules