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

/resilience-failure

@228d57d
Run it yourself

This skill should be used when the user asks about "fault tolerance", "resilience", a "circuit breaker", "graceful degradation", "retry storm" or "thundering herd on recovery", "exponential backoff with jitter", "timeout", "bulkhead", a "single point of failure" (SPOF), "failover", or "rate limiting" (token bucket / leaky bucket / sliding window). Use it whenever a design must keep working through node crashes, slow dependencies, traffic spikes, or partial outages — i.e. any time the answer to "what happens when this breaks?" is missing, even if the user doesn't say "resilience".

Use this Skill: https://skilld.dev/gh/proyecto26/system-design-skills/resilience-failure

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

referencesproviderstemporal.md

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

Resilience & failure — Temporal (durable execution)

Read this when the resilient unit of work is a multi-step, long-running process (an order, a payment flow, a provisioning pipeline) rather than a single request/response call. Temporal makes retries, timeouts, and recovery durable primitives of the workflow itself instead of ad-hoc app logic.

Service mapping (generic option → Temporal primitive)

  • Retry with backoff + jitter → an Activity RetryPolicy (initial interval, backoff coefficient, max interval, max attempts, non-retryable error types). Temporal owns the retry loop and persists attempt state, so a worker crash mid- retry resumes from the durable record, not from zero.
  • Timeout → built-in StartToClose / ScheduleToClose / Heartbeat timeouts per activity. Heartbeat timeouts detect a stuck worker on a long activity.
  • Graceful degradation / compensation → the Saga pattern: on a failed step, run registered compensating activities to undo prior steps (the distributed-transaction alternative; the saga theory is owned by consistency-coordination).
  • Recovery without stampede → workflow state is durable, so after an outage a workflow resumes deterministically from its last completed step instead of every client re-driving the whole process. No replay-the-backlog herd.
  • Rate limiting → worker task-queue concurrency limits and activity rate limits cap how fast work is pulled — backpressure rather than a 429 at the edge (edge limiting still belongs upstream).

Limits / things that bite (verify against current docs)

  • Workflow code must be deterministic — no wall-clock, random, or direct I/O in workflow functions (use activities / Temporal's SDK APIs). Non-determinism breaks replay-based recovery.
  • Event-history size and per-workflow limits are bounded; very long or high-event workflows need Continue-As-New to reset history.
  • The Temporal service/cluster (and its persistence store) is itself a dependency to make highly available — it's not magic uptime.

Provider-specific trade-offs

  • Temporal replaces hand-rolled retry/timeout/saga state machines and the brittle "where was I?" recovery logic with durable guarantees — a big win for long-running orchestration.
  • It adds an operational dependency (the cluster) and a programming-model constraint (determinism). YAGNI for a plain stateless request path — a resilience library is lighter there. Reach for it when the process, not the call, must survive crashes.

Pitfalls

  • Sneaking non-determinism into workflow code (clock, UUID, network) — passes in test, fails on replay.
  • Treating Temporal's durable retries as a license to retry non-idempotent activities without dedup — the activity still needs an idempotency key (→ api-design).
  • Letting event history grow unbounded instead of using Continue-As-New.
  • Forgetting the Temporal cluster needs the same redundancy/SPOF analysis as any other critical component.

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

    The skill provides architectural guidance for system resilience and failure handling. It contains no executable code, network operations, or sensitive data access.

  • 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/resilience-failure