Recent years have demonstrated that the scale required of our systems is anything but predictable. Moreover, when systems become overwhelmed they often fail spectacularly rather than discreetly. Unlike our need for scale, failure is predictable, and with proper design and tooling, blast radius can be contained and isolated. Isolating failure requires deliberate design, understanding of failure modes and how to compensate and contain them. Designing for failure doesn’t have to come at the expense of delivery velocity. With the right tools and tactics you can raise the bar on the resilience of your systems. In this session, Alex will lay out practices and tools to help you optimize the resilience of your systems. From containing security events to adapting to changes in scale, you will walk away with the insights you need to improve the resilience of your legacy and brownfields and greenfields alike.
Inventor, Technologist, and Engineer @LaunchDarkly
Alex Hardman (he/him) is an inventor, technologist, and engineer who spent more than a decade transforming engineering teams in large enterprises before joining LaunchDarkly. He has led teams through building mission critical systems at Liberty Mutual and Capital One and directed modernization moves to the cloud, focusing on serverless, to support the confidence and capabilities of teams and people in the process. Alex embodies his passion for software by mentoring and teaching others about new techniques and technologies and leading the charge toward improving our outcomes. As a person with ADHD, he values making the complicated uncomplicated and helping make cloud technology accessible to developers from all walks of life.
Session Sponsored By
Fundamentally change how you deliver software.