Description

Failure in our software systems is inevitable - be it a failing hard drive, broken network cable, power outage, virus, or simply a bug in the code.

"Hope is not a strategy" - thus we need to think about how we handle that failure.

Why you might be interesting in this episode:

• The differences between how failures impact our traditional monolith applications and the more modern distributed application
• To gain an understanding of the terms like Graceful Degredation, Cascading Failure, The Retry software pattern, The Circuit Breaker software pattern, and Deadline Propagation
• And advice on how to find opportunities to use them

-----

Find this episodes show notes at: https://red-folder.com/podcasts/129

Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap