Webinar Recap — Service Mesh powered chaos engineering with Gloo Shot
Thanks to those who joined our webinar last week on Service Mesh enabled Chaos Engineering with Scott Cranton and Scott Weiss. Chaos Engineering is a newer concept evolved out of the need to test for resilience in fast changing, distributed microservices. Solo.io’s Gloo Shot does this uniquely through service mesh to provide the ability to run controlled chaos experiments that do not require any changes to the application code or to import any libraries. You can watch the recording above and view the presentation here.
Here are some of the highlights of the Q&A:
What kind of experiments can I run with Gloo Shot?
We currently support two types of experiments right now; failure injection and latency. With the first one, you can inject a failure code like 404s or 500s (or whatever response you choose) to be returned when one service tries to reach another service within a cluster or to something outside our cluster like a third party service. The other is injecting latency into the responses between the services to test the latency issues of your application network.
I don’t have a service mesh deployed yet, can I still use Gloo Shot?
Gloo Shot has been designed to run in service mesh environments. The reason for this architectural decision is that then running chaos experiments are really just a configuration change versus having to modify the application code or import libraries. By having Gloo Shot part of the service mesh, it is language agnostic and can provide these capabilities across the mesh. Service Mesh Hub is a free to use dashboard that makes it easy to get started to service mesh.
Does Gloo Shot also help me troubleshoot the weakness that I found in the experiment? Gloo Shot is one in a family of application health tools in the Gloo Platform including Squash (available today) and Loop (early demo at KubeCon EU) for microservices environments. Squash is a language agnostic debugger designed specific to microservices environments that can be used to debug issues reported anytime or ones discovered during the Gloo Shot experiments. Loop is the ability to record and replay production issues, snapshot the environment and spin up a sandbox environment with Squash attached to debug production issues. Check out the KubeCon EU talk to see the demo.
We hope you enjoyed this webinar and check the schedule for an upcoming webinar or meet us at an upcoming event. If you’d like to stay informed, sign up for our newsletter or join the community to start a discussion.