Fail Faster: Adding Circuit Breakers to your APIs

on YouTube ↗25m

" summary

Shows how circuit breakers cut failed upstream calls to milliseconds instead of minutes, using concrete numbers (99.7% uptime → 0.3% of 500k = ~1,500 failures → ~$75,000/month) and real tools: Hystrix concept, JavaScript Possum implementation, Artillery load tests and DataDog metrics. Explains bucketed rolling windows (10–15s), capacity and error-threshold settings, timeout and reset timeouts, demo results where breakers fail fast or return cached fallbacks, and warns about tuning to avoid preventing container auto‑scaling.

AI-written summary · about

" chapters (14)

1. 0:00Intro
2. 0:33Scenario
3. 2:29Characteristics of a Microservice Architecture
4. 2:41Design for Failure
5. 3:17Graceful Degradation
6. 3:45Monitoring
7. 4:10Resiliency
8. 7:45Rolling Window
9. 9:07How do they work?
10. 10:56How do I use them?
11. 14:37Errors
12. 18:20Timeouts w/ Fallback
13. 20:03Gotchas
14. 21:02Going Forward

" related talks

• 16mcircuit-breaker.jsRichard Layte, Daniel Perez Alverez · JSConf EU 2013
• 51mBuilding Fault Tolerant MicroservicesKristoffer Erlandsson · Jfokus 2016
• 42mArchitecting for Failures in MicroservicesBhakti Mehta · Devoxx US 2017
• 29mFault Tolerance is a Requirement Not a Feature - Adar Danait, Lilian Ernest, CitiAdar Danait, Lilian Ernest · SpringOne Platform 2017
• 06mRetries and Circuitbreakers in Takealot MicroservicesJohan Beyers · PyConZA 2021
• 30mMaking Your Apps and Infrastructure Services Failure-Resilient with...Yaron Schneider, Henry Spang · KubeCon + CloudNativeCon Europe 2022
• 01h 01mBreaking your REST APIs to make them stronger!!Jose Luis Latorre Millas · dotnetdays 2023
• 40mLet it fail: resilience patterns for microservicesJoão Alves · Commit Conf 2019