Making microservices micro with Istio and Kubernetes
Microservices architecture can be complex to configure. If you have a polyglot environment, how would you make sure all of the stacks can address the same concerns in a consistent way? This is where a service mesh comes in!
Microservices are here to stay!
When applied properly, microservices techniques and culture ultimately help us continuously improve business at a faster pace than traditional architecture. However, microservices architecture itself can be complex to configure. All of a sudden, we are faced with the need for a service discovery server, how do we store service metadata, make decisions on whether to use client-side load balancing or server-side load balancing, deal with network resiliency, think how do we enforce service policies and audit, trace nested services calls…. The list goes on.
Sure, it’s easy to have a single stack that makes everything work provided there are good microservices support – but what if you have a polyglot environment? How would you make sure all of the stacks can address the same concerns in a consistent way? This is where a service mesh comes in. In this talk, Ray will introduce Istio, an open source service mesh framework created by Google, IBM, and Lyft. We’ll see how the service mesh works, the technology behind it, and how it addresses the aforementioned concerns.