We know we've built reliabile systems when we survive the surge of Shoppers on Black Firday or maintain uptime during a massive migration. But realibility isn't about a single moment. It's built over time with every single deployment, resulting in a relationship of trust with your users and customers. Reliablity requires practice.
We'll kick off Chaos Conf by hearing from speakers who have deployed reliability practices and built organizations that delivered for their customers during critical moments. Tune in to hear technical reliability tactics and lessons.
Examples:
More than a title: establishinig an SRE practice in your organization
Documenting your reliability practices with runbooks
Setting and achieving milestones in your reliability journey
Day 2
Completing the DevOps Loop
Wednesday, October 7
DevOps has improved the flow of software from Developers to Operations but without feedback from Ops to Devs, DevOps is incomplete.
Learn how Chaos Engineering completes the loop to deliver more reliable products and services.
DevOps is supposed to tear down the silos separating developers and operations engineers. But too often, it creates a one-way flow from developers to ops with no feedback from ops to help developers build more operable and reliable applications. Chaos Engineering provides a way to complete the loop and prioritize quality across all teams.
Day two of Chaos Conf will cover how to help your organizations meet reliability goals by including Chaos Engineering in the software lifecycle.
Examples:
Setting Service Level Objectives (SLO's) and Validating Indicators (SLI's) with Chaos Engineering
Moving from manual Gamedays to automated Chaos Experiments
Chaos Engineering in your CI/CD Pipeline
Code isn't done when you deploy it - Building reliability and operability into software
Holistic systems: bringing Developers and Operations Engineers together with Chaos Engineering
Day 3
A Data-Driven Culture of Reliability
Thursday, October 8
The software we build reflects the engineering culture of our organizations.
Learn how to build a culture of reliability that results in more reliable systems and applications.
Cultural change on the organizational level requires data to back it up. To grow an internal culture of chaos experimenation, you must democratize what you're learning. But how do we capture and share the most important lessons? How do you influence building a culture of reliablity?
Day three will cover what to measure, and how to use that data to tell stories that influence change across your organization.
Examples:
Using your monitoring data to guide chaos testing and verify test success
Reliability vs Features: Using Chaos Engineering to prioritize work
Celebrating wins - Case studies featuring how Chaos Engineering led to reduced incidents, lower MTTR, and other desired business outcomes.
Interested in Speaking?
The call for papers is now open!
Submit your ideas by August 14th.
