When you’re designing a distributed system you have to think through all the possible failure modes and interactions. Have a plan in place not for if something goes wrong, but for when something goes wrong.
“Distributed systems tend to be more complicated if we decide we don’t want to blissfully ignore failures”
If you design a system with the assumption that failure is going to happen, you can gracefully recover from any challenge and ensure you’re resilient without jeopardizing the business or the user’s experience. Headspring’s Chief Architect, Jimmy Bogard, presents on “Fixing Distributed Systems Fail.” This session takes a closer look at:
- The way distributed systems and microservices can fail
- The side effect of when something goes wrong and the impact on the end user
- The many options for coordinating activities between multiple systems in a single app
- Balancing business needs and what’s possible with the resources you have
- How to move the broken system into a resilient one, embracing (instead of ignoring) the fallacies of distributed computing