Service Mesh

You're in an IT department. How does the rest of the organization see you? As a valuable asset whose code and APIs make a difference in the marketplace, or as a necessary evil that should be trimmed wherever possible? Containers, microservices, and serverless computing can get you where you need to go.

About a year ago Red Hat announced its participation as a launch partner of the Istio project. We are now introducing the istiooc command-line tool and a set of pre-built Istio and Jaeger example scenarios that would make it even easier to get started with these technologies.

The past nine weeks of blog posts have introduced, explained, and demonstrated some of the many features of the Istio service mesh when combined it is with Red Hat OpenShift and Kubernetes. This, the final post in this series, is a recap.

Using Istio with Red Hat OpenShift and Kubernetes makes life with microservices easier. But what if you want your microservice to talk to another service that is outside of your OpenShift/Kubernetes/pods environment? Enter Istio Egress.

Burr Sutter (@burrsutter) and I (@christianposta) have finished writing a small book to help folks get up and running with Istio.io service mesh! Download the complimentary e-book at developers.redhat.com.

This is part eight of a ten-week series and covers using the Canary Deployment pattern to ease code into production. Istio makes this easy while giving you several good options for intelligent routing. And you can do it all without changing your source code.

Discover how using Istio with OpenShift and Kubernetes eases microservices production and deployment. (Part 7 of 10 in a series)

Everything you need to coordinate microservices in a service mesh with the

In this post, we will deploy the existing Coolstore microservices demo as a service mesh and start to demonstrate the tangible value you can get out of the system without any major rewrite or rearchitecture of the existing app. We'll also improve our project along the way to adhere to Istio best practices.

Testing software is challenging and very important. Testing for correctness is one thing, but testing for failures in network reliability is quite another task. This article will demonstrate how Istio makes this oh so easy.

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.