Building for Gracious Failure
summary
Everything fails some of the time and the concrete wins: add Bugsnag and SignalFX to move from noisy logs to metrics that reveal staging jobs are 100% failing, use LogRocket to tie errors to user actions, migrate millions of data points carefully and avoid YAML/Psych parser crashes by returning null for corrupt values, design services to accept partial inputs, and stop trusting dependencies blindly to prevent a distributed‑monolith cascade.
AI-written summary · about
chapters (4)
related talks
42mPlanning To Fail
01h 06mCongratulations, you Failed!
28mBuilding Resilient DevOps Pipelines: Strategies for Handling Unexpected Failures &...
20mDoing Things the Hard Way
36mFailing With Grace
51mDesigning for Failure: Build Resilient Services
29mEmbracing Failures to Avoid Meltdown
29mLooking under the rug: the art of learning from failure
