Developers are moving away from large monolithic apps in favor of small, focused microservices that speed up implementation & improve resiliency. Microservices & containers changed application design & deployment patterns, but along with them brought challenges like service discovery, routing, failure handling, & visibility to microservices.
"Service mesh" architecture was born to handle these features. Applications are getting decoupled internally as microservices, & the responsibility of maintaining coupling between these microservices is passed to the service mesh.Istio, a joint collaboration between IBM, Google & 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 meetup we will see how istio can be used to manage traffic in a demo application running microservices.
If you attend, you can expect to learn:
* Why kubernetes needs service mesh
* How Istio improves network traffic management
* How to use Istio
- 6:30-7pm - Doors Open for Networking & Food
- 7-8pm - Main Presentation
- 8-830pm - Q&A + Networking
- 9pm - Venue closes
Interested in exploring IBM Cloud? Join via:
About the Presenter
Mofizur Rahman (@moficodes) is a Developer Advocate at IBM. His area of interests include container orchestration, micro services & blockchain. His favorite programming language these days is Go. He also tinkers with Node, Python & Java. He is also learning & teaching in the Go, Kubernetes & Hyperledger Fabric community. He is a strong believer of the power open source & importance of giving back to the community. He is a self proclaimed sticker collecting addict & has collected several box full of stickers with no signs of stopping. He dabbles in photography sometimes.