CodeOpinion

0 subscribers

⏱ 👁 1,285 views

Why "Resilient" Systems Crash Under Pressure

Video Overview & Insights

Most developers think slapping retries and circuit breakers makes a system resilient. It doesn't and can often backfire. Retries aren't free and they consume resources. "Slowness" is often more dangerous than a complete failure.

🔗 Kurrent

https://kurrent.io

🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1

💥 Join this channel to get access to a private Discord Server and any source code in my videos.

🔥 Join via Patreon

https://www.patreon.com/codeopinion

✔️ Join via YouTube

https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join

📝 Blog: https://codeopinion.com

👋 Twitter: https://twitter.com/codeopinion

✨ LinkedIn: https://www.linkedin.com/in/dcomartin/

📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeopinion

0:00 Intro

0:56 Example: Worker Queues & Failure Modes

2:08 Why "Slowness" is Worse Than "Down"

4:09 Not All Failures are Equal

5:54 Retries are Not Free

7:21 Resource Exhaustion & Backlogs

8:14 Using Metrics for Global Resilience

9:26 The Resilience Decision Tree (Key Takeaway)

11:05 Summary: Understanding Trade-offs

#software architecture #software design #cqrs #event sourcing #design patterns #software architect #programming #.net #.net core #asp.net #asp.net core #soa #microservices #message queues #kafka #event bus #event driven architecture #azure service bus #rabbitmq #distributed transactions #service bus #mass transit #nservicebus #message queue #message queuing #messaging patterns #service oriented architecture #microservice architecture #domain-driven design #enterprise service bus