Developers are moving away from large monolithic apps in favor of small, focused microservices that speed up implementation and improve resiliency.

Microservices and containers changed application design and deployment patterns, but along with them brought challenges like service discovery, routing, failure handling, security and visibility to microservices.

“Service mesh” architecture was born to handle these features. Applications are getting decoupled internally as microservices, and the responsibility of maintaining coupling between these microservices is passed to the service mesh.

Istio, a joint collaboration between IBM, Google and Lyft provides an easy way to create a service mesh that will manage many of these complex tasks automatically, without the need to modify the microservices themselves.

In this online meetup, we will see how istio can be used to manage traffic in a demo application running microservices. We will learn why kubernetes need “service mesh” and how does Istio improve network traffic management.

Mofizur Rahman (@moficodes) is a Developer Advocate at IBM. His area of interests include container orchestration and micro services. His favorite programming language these days is Go. He also tinkers with Node, Python and Java. He is also learning and teaching in the Go, Kubernetes, Docker and Microservice community. He is a strong believer of the power open source and importance of giving back to the community. He is a self proclaimed sticker collecting addict and has collected several box full of stickers with no signs of stopping. He dabbles in photography sometimes.

He writes tech blogs at NYCDEV medium page which can be found on https://medium.com/@moficodes

Managing Kubernetes Traffic with Istio