The Design of Error
summary
Design errors into products by modeling failure as part of workflows rather than just catching exceptions. Techniques covered include the saga pattern for business-level compensation, circuit breakers with backoff and retries for external calls, centralized logging to trace failures across microservices, and caches or fallback values to keep user flows moving; these patterns reduce support tickets and maintain consistency by treating errors as alternative branches in the user journey.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:31Rethinking error concept
- 7:46Application errors and feedback
- 10:52Runtime error handling
- 16:49Errors in distributed systems
- 21:41Circuit breakers and UX
- 26:56Saga pattern for errors
- 29:06System design against errors
- 32:17Corps-loop: critical errors
- 35:47Conclusion
related talks
51mDesigning for Failure: Build Resilient Services
36mThe Arcane Art of Error Handling
03mRecap
29mLooking under the rug: the art of learning from failure
35mDesign patterns for application resiliency
34mHow to Teach a Service to Report Errors So They're Clear to Users and Machines
16mEngineering Failure-Resilient Systems
53mResiliency and Availability Design Patterns for the Cloud