#resilience

  • Circuit Breaker
    Describes the Circuit Breaker pattern, which stops a caller from repeatedly calling a failing or slow service, its three states, and how to build it on AWS.
  • Retry With Backoff
    Describes the Retry with Backoff pattern, which automatically retries operations that failed from transient errors using exponential backoff and jitter, with AWS implementations.
  • Bulkhead Pattern
    Explains how isolating application components into separate resource pools keeps a failure or overload in one pool from cascading, with a Kubernetes resource-limit example.
  • Circuit Breaker Pattern
    Explains how a circuit-breaker proxy with Closed, Open, and Half-Open states stops an application from repeatedly calling a failing remote service and prevents cascading failures.
  • Rate Limiting Pattern
    Control resource consumption by capping the rate of access to a capacity-limited service, avoiding throttling errors and keeping throughput predictable.
  • Retry Pattern
    Handle transient failures when connecting to services or network resources by transparently retrying failed operations, with backoff and idempotency in mind.
  • Scheduler Agent Supervisor Pattern
    Coordinate a set of distributed actions as a single operation, with a scheduler, agents, and a supervisor that recovers or compensates failed steps.
  • Throttling Pattern
    Control resource consumption per application instance, tenant, or service so the system keeps meeting its SLAs under sudden demand spikes.
  • Retry And Circuit Breaker
    Covers retry with gradual backoff, the Circuit Breaker pattern, distributed transaction techniques such as SAGA, and the Outbox pattern for reliable messaging.