Service Mesh in Practice
One of the most complex challenges in realizing microservice architecture is not building the services themselves, but building and governing the communication between services. Most microservices developers have to take care of complex inter-service communication logic as part of their service development.
Service Mesh has emerged as a solution to overcome the challenges that we have in microservices communication. Since most of the inter-service communication requirements are quite generic across all microservices implementations, we can think about offloading all such tasks to a different layer, so that we can keep the service code independent.
In this session, David and Kasun will discuss the following:
- Why we need a Service Mesh?
- Fundamentals of Service Mesh
- Introduction to Istio
- What's new in Istio 1.0.
- Seamless integration of Ballerina and Istio
Product Manager, Google Cloud Platform
David is a product manager on the Istio project at Google Cloud Platform. He brings over two decades of enterprise and service provider wireless and distributed systems to Istio. David hails from Australia and loves motorbikes and the great outdoors - be it the Southern Cross or the amazing Californian terrain.
Director – Integration Architecture, WSO2
Kasun is a key member of WSO2’s architecture team that drives development efforts of WSO2 integration platform. Previously, he was involved in developing WSO2 Enterprise Service Bus as a product lead of WSO2 ESB and he has authored the book, “Beginning WSO2 ESB”. He is an elected member of the Apache Software Foundation and a Project Management Committee member and a committer for the Apache Synapse open source ESB project. Kasun has provided technology consulting on numerous customer engagements by helping to successfully design and implement solutions for integrating Web Services, REST, SAP and various other technologies.