October 24, 2019

204 words 1 min read

Chaos Debugging: Finding and Fixing Microservice Weak Points

Chaos Debugging: Finding and Fixing Microservice Weak Points

Distributed microservices introduce new challenges: failure modes are harder to anticipate and resolve. In this session, we present a Chaos Debugging framework enabled by three open source projects: …

Talk Title Chaos Debugging: Finding and Fixing Microservice Weak Points
Speakers Mitch Kelley (Software Engineer, Solo.io), Idit Levine (Founder & CEO, Solo.io)
Conference KubeCon + CloudNativeCon Europe
Conf Tag
Location Barcelona, Spain
Date May 19-23, 2019
URL Talk Page
Slides Talk Slides
Video

Distributed microservices introduce new challenges: failure modes are harder to anticipate and resolve. In this session, we present a “Chaos Debugging” framework enabled by three open source projects: Gloo Shot, Squash, and Loop to help you increase your microservices’ “immunity” to issues.Gloo Shot integrates with any service mesh to implement advanced, realistic chaos experiments. Squash connects powerful and mature debuggers (gdb, dlv, java debugging) to your microservices while they run in Kubernetes. Loop extends the capability of your service mesh to observe your application and record full transactions for sandboxed replay and debugging.Come to this demo-heavy talk to see how together, Squash, Gloo Shot, and Loop allow you to trigger, replay, and investigate failure modes of your microservices in a language agnostic and efficient manner without requiring any changes to your code.

comments powered by Disqus