Index of every page on this site: llms.txt
All skills
proyecto26 avatar

/service-decomposition

@228d57d
Run it yourself

This skill should be used when the user asks "monolith vs microservices", how to "split into services", set "service boundaries", find the right "service granularity", design an "API gateway / BFF", do "service discovery" or add a "service mesh", or worries that services are "too chatty" / "too fine-grained" — including when a team is pushed to adopt microservices or Kafka between services "to be ready to scale" and the right answer may be a modular monolith. It gives the recipe for carving a system into services (or deciding not to) and wiring how they find and call each other. Use it whenever a design has more than one service — or someone is tempted to add more — even if the user doesn't say "microservices".

Use this Skill: https://skilld.dev/gh/proyecto26/system-design-skills/service-decomposition

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesprovidersazure.md

≈376 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Service decomposition — Azure

Service mapping

  • Compute for services — AKS (Kubernetes), Container Apps (managed containers + built-in Dapr/KEDA), or Functions for event-driven services.
  • API gateway / front door — API Management (full gateway: auth, throttling, versioning) or Application Gateway / Front Door for routing.
  • Service discovery — Kubernetes DNS on AKS; Container Apps service discovery; Dapr name resolution.
  • Service mesh — Istio-based add-on for AKS, or Open Service Mesh; Dapr as a sidecar for service invocation, pub/sub, and state.
  • Cross-service workflows / saga — Durable Functions or Logic Apps (orchestration); transactional outbox via Service Bus + change feed.

When to pick which

Container Apps + Dapr for a fast managed microservices start; AKS when you need full Kubernetes/mesh control; API Management when you need a policy-rich gateway; Durable Functions for orchestrated sagas.

Limits / things that bite (verify against current docs)

  • API Management tiers differ sharply (no VNet/SLA on Consumption; cost on Premium).
  • Dapr adds a sidecar (latency/ops) though it simplifies invocation/pub-sub.
  • Front Door / App Gateway routing + WAF add hops and config surface.

Pitfalls

  • Treating Logic Apps/Durable as a place for core business logic.
  • Mixing Dapr and a separate mesh without a clear division of responsibility.
  • Cross-service ACID expectations — use saga/outbox, not distributed transactions.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    This skill provides architectural guidelines for service decomposition and microservices design. It is purely informational, contains no executable code, and poses no security risk.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at 228d57d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago

README badge

README badge for proyecto26/system-design-skills/service-decomposition