Design Patterns to survive major outages

My system was indirectly affected by the Crowdstrike incident. Here's the design patterns used and things to consider to make your system more resilient to failures.
🔗 EventStoreDB
eventsto.re/co...
🔔 Subscribe: / @codeopinion
💥 Join this channel to get access to a private Discord Server and any source code in my videos.
🔥 Join via Patreon
/ codeopinion
✔️ Join via UA-cam
/ @codeopinion
📝 Blog: codeopinion.com
👋 Twitter: / codeopinion
✨ LinkedIn: / dcomartin
📧 Weekly Updates: mailchi.mp/63c...

[@liquidsnake6879]

It's always great when you have control of the entire domain and can plan out such fallbacks from backend to frontend, more reason why full stack is the way to go, in my company even setting up such a fallback would lead to 20 meetings with different teams across different domains, and as a result would never get done lol the human entropy is real.

[@CodeOpinion]

Ya, that's a good point. Working in a small team with ownership/authority, even if that's in a large organization (or not) you often have this ability. I can see how it can be incredibly frustrating if you don't.

[@metaphoricallyspeaking]

I've just shared this video to a few places. Feels very 'off the cuff', unscripted and good advice. Maybe it's because I'm working in a highly regulated industry and focusing on these things was why it resonated, but I loved this one and I thought I'd let you know!

[@CodeOpinion]

Thanks for sharing and the comment. It is unscripted, I'm just blabbing about talking points I have in mind.

[@pierrelautrou1210]

Great video about strategies that can be leveredged to improve the resilience of a system.
In my opinion everything you said about 3rd party systems can also apply to a system internal components and when you gave the exemple of the currency exchange rate I thought you'd talk about caching.

[@CodeOpinion]

Ya I've covered that before in another video. But yes, absolutely applies to your own internals like caching