Learning on Web Dev Open is free for all.

System Design & Performance > Scale, consistency and failureDegrading on purpose
Phase 06Scale, consistency and failure317 of 434

Degrading on purpose

Turn off a dependency in your own application and make the failure a smaller product rather than an error page.

Build45 minAI adversary

Build this in your own editor

This one runs on your machine rather than in the browser workbench. Work to the outcomes below, then come back and mark it complete.

You should now be able to

  • Add a timeout and a fallback to a non-critical dependency
  • Implement a circuit breaker or a feature switch for degradation
  • Specify the reduced experience rather than improvising it
Ask the community

Loading…

← PreviousMore than one region, and why you might not want itScale, consistency and failureNext →Logs you can query at three in the morningSeeing it, and paying for it