Microservices Architecture

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

Use this parent skill as the active microservices entrypoint. It should help decide whether microservices are justified, then shape service boundaries and operating contracts when they are.

Use When

• Defining service boundaries, ownership, API contracts, data ownership, deployment independence, or migration from a monolith.
• Reviewing synchronous and asynchronous service communication, reliability, retries, idempotency, and failure isolation.
• Creating a target architecture for teams that need multiple independently deployable backend services.

Do Not Use When

• The task is unrelated to this parent skill or is better handled by a narrower active parent named in the workflow.
• The request only needs a trivial answer and no reference module needs to be loaded.

Required Inputs