Service Mesh

distributed architectures introduce more complexity, services meshes can help soften the landing and shift some of that complexity out of our applications and place it where it belongs, in the application operational layer: Bringing Coolstore Microservices to the Service Mesh: Part 1 - Exploring auto-injection

Istio brings tracing and monitoring to your system with very little effort, helping you keep things humming. This article covers Istio Tracing & Monitoring: Where are you are and how fast are you going?

The phrase "Failure is not an option" is tossed about with much bravado, with Istio Circuit Breaker. But the fact remains, things eventually fail. Everything. How, then, do you handle the inevitable failure of your microservices? This article will show you how.

This is week three of a ten-week series about Istio, kubernetes and OpenShift. The series started with an introduction to Istio, and this week covers Istio Circuit Breaker: How To Handle (Pool) Ejection.

This article covers Istio Route Rules and telling Service Requests Where To Go. OpenShift and Kubernetes do a great job of working to make sure calls to your microservice are routed to the correct pods. What if, however, you want to customize the routing?

this is an introduction to Istio. Istio helps automate the developer time to implement a feature. The combination of code complexity and code heft (i.e. number of lines of code) can put a drag on an implementation. Istio is a better way.

In this session, we will give you a taste of Envoy and Istio, two open source projects that will change the way you write distributed, cloud native, Java applications on Kubernetes.