2021 Call for Code Awards: Live from New York, with SNL’s Colin Jost! Learn more

KEYNOTE: Architecting for Reliability Presentation

Abstract

In a world where businesses provide services across the globe, the demand for availability is ever increasing. This is even more true for the expectation on availability and performance from a user perspective – services need to be always-on. Reliability describes the ability of a system or component to function under stated conditions for a specified period of time. Reliability cannot simply be delegated to the infrastructure and/or platform a service is running on. Every tier needs to provide their contribution towards the reliability of the entire system. Also, reliability cannot be added after the fact on top of a built system, the system and its components need to be designed and implemented with reliability in mind. It is a shared responsibility by everyone contributing to the Software Development Lifecycle, including the Architect, the Product Owner, the conscientious DevOps Engineer, and the empowered SRE.

This presentation describes key architectural patterns available to implement reliability into a software component or service. With the skill and experience in these techniques, the engineering professional can have a meaningful conversation with product owners on implementing reliability targets for a given service.

Speaker Bio

BIO – Ingo Averdunk is a Distinguished Engineer in Service Management and Site Reliability Engineering (SRE). Ingo develops architectures and performs RedTeam and Design Thinking sessions globally, and is on the IBM D/A/CH Technical Leadership team.