Service Boundary Design

Decide whether deployable service boundaries should be kept, split, merged, strengthened, or replaced by an in-process module boundary. Use for microservice proposals, modular-monolith reviews, service sprawl, unclear data ownership, cross-service pain, incidents, or ownership realignment. Ground recommendations in domain, change, data, runtime, failure, and operating evidence; route module details to deep-module-design.

zhuochun Updated 1 repo stars

File contents

zhuochun/skills commit 188e2e0057

Frequently asked questions

npx get-skill add zhuochun/service-boundary-design