Cloud-based distributed applications have changed how we need to approach reliability and resiliency. How do you make your applications reliable? Here’s Gremlin CEO Josh Leslie to tell you how. Today’s dynamic applications are too complex and constantly changing for humans to wrap their heads around. This means the reliability approaches that worked ten years ago simply won’t be enough. As a technology company (and these days, every company is a technology company), you need to take a different, programmatic approach to testing and improving the reliability of your applications.

80% of failures at the infrastructure layer come from the same core gaps in reliability. Jeff Nickoloff, Gremlin Principal Engineer, goes over how Reliability Management test suites help improve reliability across your organization. Are you waiting for the other reliability shoe to drop and hoping that you actually fixed core resilience issues? Or do you know for sure that you’re resilient to common reliability issues?

Part of the Gremlin Office Hours series: A monthly deep dive with Gremlin experts. To get the most value out of Chaos Engineering and reliability testing, you need a way to observe your service’s behavior. Observability tools offer insight into how your systems are performing, but observability on its own isn’t enough. You need a way to monitor your systems while testing their reliability so you can determine whether your service passed or failed a test.

Unreliable software can have a painful impact on your customers and your business—something we’ve all seen and felt during high-profile outages. And while building on the cloud with AWS unlocks improved scaling and reliability capabilities, the complexity of modern distributed systems can potentially introduce outage-causing reliability risks. How can you be sure your systems are resilient to failure when they’re based on complex architecture, built by hundreds of teams, and are being updated almost constantly?