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.

referencesprovidersaws.md

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

Service decomposition — AWS

Service mapping

  • Compute for services — ECS/Fargate or EKS (containers), or Lambda (functions) for event-driven/spiky services.
  • API gateway / front door — API Gateway (REST/HTTP/WebSocket, auth, throttling) or ALB (path/host routing) for simpler container fronting.
  • Service discovery — AWS Cloud Map (+ ECS Service Connect); EKS uses Kubernetes DNS.
  • Service mesh — App Mesh (Envoy-based) or self-managed Istio on EKS.
  • Cross-service workflows / saga — Step Functions (orchestration) or EventBridge (choreography); transactional outbox via DynamoDB Streams.

When to pick which

ALB for plain container routing; API Gateway when you need managed auth/throttle/ usage plans; Lambda + EventBridge for event-driven services; Step Functions when a multi-service write needs orchestrated compensation (saga).

Limits / things that bite (verify against current docs)

  • API Gateway adds latency + per-request cost and has payload/timeout limits (e.g. ~29s integration timeout) — not for long-running calls.
  • App Mesh/Envoy sidecars add latency and operational surface.
  • Cloud Map / Service Connect health-check + DNS TTL lag affects failover speed.

Pitfalls

  • API Gateway accreting business logic (mappings/transforms) into a hidden monolith.
  • Lambda for chatty synchronous chains → cold starts + fan-out latency.
  • Cross-service ACID expectations — use Step Functions/saga, not 2PC.

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