INTERMEDIATE · 8 MODULES · 64 LESSONS

Resilience and Reliability Patterns

Keep your system standing when one of its parts fails, with timeouts, retries, idempotency, circuit breakers, and graceful degradation, measured before and after.

For you if
Your service depends on APIs or services that sometimes fail or slow down.
By the end
You'll know when to retry and when not to, how to avoid double charges, and how to stop a cascading failure.
You need
Basic Python and a service you've built that calls another API. Everything is simulated in Python.
  1. 01Por qué fallan los sistemas distribuidos8 LESSONS
    1. Module introduction: the day `shipping` took down the whole checkout
    2. Partial failure: in distributed systems, something is always broken
    3. The fallacies of distributed computing
    4. Cascading failure: how a slow dependency takes everything down
    5. Pool exhaustion: why a slow `shipping` exhausts `orders`' threads
    6. Why the monolith didn't have this problem
    7. The map of Mercado's checkout failure points
    8. Mini-project: map the failure modes of Mercado's checkout
  2. 02Timeouts8 LESSONS
    1. Module introduction: the silent killer
    2. What is a timeout
    3. Pool exhaustion without timeouts
    4. Connection timeout vs read timeout
    5. Choosing the value from the p99
    6. The timeout as a time contract
    7. Chained timeouts and the time budget
    8. Project: put timeouts on Mercado's checkout and measure
  3. 03Reintentos, backoff y jitter8 LESSONS
    1. Module introduction: the timeout left you a decision
    2. Why retry (and why it works)
    3. The retry storm, measured
    4. Exponential backoff
    5. Jitter and de-synchronization
    6. Retry budget
    7. When NOT to retry
    8. Project: correct retries for Mercado's calls
  4. 04Idempotencia8 LESSONS
    1. Module introduction: the retry that charges twice
    2. The retry's double charge, measured
    3. The idempotency key
    4. How the server deduplicates and saves the result
    5. Operations idempotent by design
    6. PUT vs POST vs GET
    7. The exactly-once myth
    8. Project: make Mercado's `charge` idempotent and test it with retries
  5. 05Circuit breakers8 LESSONS
    1. Module introduction: stop hitting a dead one
    2. The cost of keeping calling a dead one, measured
    3. The three states of the circuit breaker
    4. From CLOSED to OPEN: opening by threshold
    5. HALF_OPEN and automatic recovery
    6. Circuit breaker vs. retry: insisting vs. giving up
    7. Choosing the threshold and the cooldown
    8. Project: put a breaker on `shipping` in Mercado and measure
  6. 06Bulkheads y aislamiento8 LESSONS
    1. Module introduction: the watertight compartments
    2. The shared-pool contagion
    3. What is a bulkhead
    4. A sub-pool per dependency
    5. The Titanic analogy
    6. Isolating by traffic class
    7. The cost of isolation
    8. Project: isolate Mercado's checkout dependencies and measure
  7. 07Degradación elegante y load shedding8 LESSONS
    1. Module introduction: fail soft, not hard
    2. Fail soft, not fail hard
    3. Critical vs non-critical
    4. The fallback value
    5. Defer and enqueue non-critical work
    6. Feature toggles and kill switches
    7. Load shedding and priority
    8. Project: make Mercado's checkout degrade instead of falling
  8. 08Proyecto — haz resiliente el checkout de Mercado8 LESSONS
    1. Module introduction: the return trip
    2. Measure the unprotected baseline
    3. Contain the blast with timeouts
    4. Make `payments` retry without charging twice
    5. Isolate and cut off `shipping`
    6. Degrade and shed to stay up
    7. Measure the before and after
    8. Project: make Mercado's checkout resilient
Reviews

What students say

These reviews are from enrolled students who completed at least 50% of the course. We moderate reviews only on content grounds (spam, offensive language, personal data), never for being critical or negative.

No approved reviews yet.

Be the first to share your experience!

SEC. 06 · THE STUDIO

Why this studio exists

For decades, building software belonged to technical profiles with years of training, and getting a digital product into the real world took companies months or years. No-code and AI have narrowed that gap, but the knowledge is still held by a few.

Tech Benders exists to open that knowledge up, so business teams and non-technical teams can put their ideas into production with the right technical decisions behind them. AI does what you ask of it. Without a technical base, what it builds may not scale with your company’s ecosystem, and its costs can run away over time.

The team knows the pains of large organizations and the speed at which they have to move. It brings solution architecture, data engineering, product built end to end from back end to front end, and daily work with AI. Software that solves what you need in days, not months, with the cost of AI kept in check.

Founders

The studioRead about Tech Benders →

Write to ushi@techbenders.io

Made with Wislab