Chaos debugging: Finding and fixing microservice abnormalities
Mitchell Kelley and Scott Cranton explain how to use open source tooling to inject, debug, and diagnose abnormal conditions in your microservices architecture.
|Talk Title||Chaos debugging: Finding and fixing microservice abnormalities|
|Speakers||Mitchell Kelley (Solo.io), Scott Cranton (Solo.io)|
|Conference||O’Reilly Open Source Software Conference|
|Conf Tag||Fueling innovative software|
|Date||July 15-18, 2019|
Building microservices applications introduces more complexity into your architecture. Highly distributed applications on elastic, ephemeral infrastructure that communicate heavily over the network make for an environment where an application is always in a fluid, partially failing state at all times. To help developers transition from the monolithic way of designing and building software to a more service-oriented approach, we need to bridge the gap in tooling to help diagnose and understand what a normal state looks like and how to recover from a non-normal state. Mitchell Kelley and Scott Cranton discuss the types of failures that can occur, namely networking, application behavior/code, and storage, and present a systemic workflow for prodding and exploring a system to detect faults and abnormal behavior. This framework builds on the practices known as chaos engineering. Mitchell and Scott take a look at two open source projects that aim to complement this workflow: the Squash project, for step-by-step distributed microservices debugging, and Gloo Shot, a newly created chaos engineering framework.