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.

referencesprovidersgcp.md

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

Service decomposition — GCP

Service mapping

  • Compute for services — GKE (Kubernetes), Cloud Run (managed containers, scale-to-zero), or Cloud Functions for event-driven services.
  • API gateway / front door — API Gateway (managed) or Apigee (full API management); Cloud Load Balancing for routing.
  • Service discovery — Kubernetes DNS on GKE; Cloud Run service URLs; Traffic Director for mesh-managed discovery.
  • Service mesh — Anthos Service Mesh / Traffic Director (Envoy-based) or self-managed Istio on GKE.
  • Cross-service workflows / saga — Workflows (orchestration) or Pub/Sub (choreography); transactional outbox via Pub/Sub + a DB change stream.

When to pick which

Cloud Run for stateless services you want managed + scale-to-zero; GKE when you need full Kubernetes/mesh; API Gateway for lightweight fronting, Apigee for rich API management; Workflows for orchestrated sagas.

Limits / things that bite (verify against current docs)

  • Cloud Run request timeout cap and cold starts affect chatty synchronous chains.
  • Apigee is powerful but heavy/costly; API Gateway is lighter but less featured.
  • Traffic Director / Anthos Service Mesh add Envoy overhead and config surface.

Pitfalls

  • Cloud Functions for deep synchronous fan-out (cold-start + latency stacking).
  • One Cloud SQL instance shared across services (distributed monolith).
  • Expecting cross-service ACID — use saga/outbox via Workflows/Pub-Sub.

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