Solo.io Agenda @OSCON
The Solo.io team is headed to Portland for OSCON and we are excited to spend the week learning and connecting with the community about open source technology. At Solo.io we not only open source developer and operator tools for Kubernetes and Service Mesh environments, we also participate in the communities of open source projects like Envoy Proxy, Kubernetes and more. If you are interested in getting involved in open source, we’d love to have you start with us — check out our projects on GitHub today.
While at OSCON, make sure to….
- All Week: Visit booth #425 for a #SoloSelfie, swag and demo
- Tuesday: Check out the local PDX Cloud Native Meetup group’s Kubernetes Release Anniversary Party
- Wednesday: Go to Christian Posta’s talk titled “Navigating the Service Mesh Landscape with Istio, Consul Connect and Linkerd”
- Thursday: Check out Mitch Kelley and Scott Cranton’s talk “Chaos Debugging: Finding and Fixing Microservice Abnormalities”
Talk: Navigating the Service Mesh Landscape with Istio, Consul Connect, and Linkerd
Date & Time: Wednesday, July 17th at 11:00–11:40am | Learn More
Christian Posta, Solo.io field CTO will share how service mesh has hit the cloud native computing community like a storm, and we’re starting to see gradual adoption across the enterprise. There are a handful of open source service mesh implementations to choose from including Istio, Consul Connect, and Linkerd.
This talk details why and when you may want to use a service mesh versus when you may want to just stick with a library, NetflixOSS, or application approach. He digs into three popular open source service mesh implementations and explores their goals, strengths, and weaknesses. You’ll come away with a good foundation from which to explore service mesh technology and ask the right questions to get to the right answer for them.
Talk: Chaos Debugging: Finding and Fixing Microservice Abnormalities
Date & Time: Thursday, July 18th at 11:50–12:30pm | Learn More
Join Mitch Kelley and Scott Cranton in this talk about how to proactively find and fix issues. Building microservices applications introduces more complexity into our architecture. Highly distributed applications on elastic, ephemeral infrastructure that communicate heavily over the network makes for an environment where an application is always in a fluid, partially failing state at all times. To help our 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.
In this talk, we introduce the audience to the types of failures that can occur, namely networking, application behavior/code, storage, etc 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. We take a look at two open-source projects that aim to complement this workflow with step-by-step distributed microservices debugging with the Squash project and a newly created chaos-engineering framework called Gloo Shot.
See you in Portland!BACK TO BLOG