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.

referencesprovidersgeneric.md

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

Service decomposition — generic / self-hosted

The vendor-neutral default. When no cloud is named, this is the answer.

What to run

  • Monolith / modular monolith — any framework; enforce module boundaries with package/build structure (e.g. separate modules, no cross-module DB access).
  • Comms — REST/JSON for breadth; gRPC for internal high-throughput typed calls; events via Kafka/RabbitMQ for async (→ messaging-streaming).
  • API gateway — Nginx, Kong, Envoy, or Traefik (auth, routing, rate limiting).
  • Service discovery — Consul, etcd, or ZooKeeper as a registry; or DNS-based (e.g. Kubernetes Services).
  • Service mesh — Istio or Linkerd (Envoy sidecars: mTLS, retries, traffic shaping, telemetry).

Topology

Clients → gateway → services (each owning its data store) → async via a broker. On Kubernetes, Services + DNS give discovery for free; add a mesh only when uniform mTLS/retries/observability across many services justify the overhead.

Limits / things that bite

  • Each sync hop ≈ a same-DC round trip plus the callee's work; deep call graphs blow latency budgets.
  • A registry or gateway is a SPOF unless replicated; cache discovery client-side.
  • Mesh sidecars add per-call latency and a real ops burden — not free.

Pitfalls

  • Sharing one database across services (distributed monolith).
  • Splitting before a real driver (deploy/scale/ownership) exists.
  • No distributed tracing → undebuggable cross-service failures.

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