Building Resilient Systems - Serverless WebDev
summary
Explains how to apply chaos engineering to serverless web apps by simulating service outages (auth, DB, cache) using simple failure injections, and measuring user-facing effects on a React/Angular front end; shows a music-streaming microservice diagram with cache to keep playback fast and a scenario where auth fails but streaming still works; demonstrates a LinkedIn-like page that hides or shows the follow button based on whether profile data is available to enforce graceful degradation; mentions homegrown chaos tools to run these experiments.
AI-written summary · about
chapters (9)
- 0:00intro
- 0:22preamble
- 0:39whoami
- 1:02what is chaos engineering?
- 4:07chaos on the frontend
- 9:16handling failures and building resilient systems
- 13:09deep dive, a linkedin usecase
- 18:11how can i create chaos?
- 18:32questions?
related talks
24mBreaking Serverless Things on Purpose: Chaos Engineering in Stateless Environments
44mApplying principles of chaos engineering to serverless
49mPerforming Chaos in a Serverless World
34mChaos engineering for serverless
43mApplying the Principles of Chaos to Serverless
51mConfusion In The Land Of The Serverless
26mContinuous Chaos in DevOps
39mBuilding Resilient Serverless Applications