Folks dealing with micro-services would have probably heard about Mesh and how it has proved to be critical component of the cloud native stack. Developers can focus on business logic and communication capabilities can be achieved using Mesh.

Mesh is a mechanism build to manage communications, configure routing strategies (FQDN/Header based), helps configuring egress route timeouts, retries, building fail-over mechanism, etc between various individual services.

Istio is an open source implementation of Service Mesh developed by Google and internally works by deploying an extended version of Envoy as proxies to each micro-service.

Envoy serves trillion of daily requests and has been adopted by thousands of renown organisations around the world.

I will talking about different use-cases of Istio such as Configuring Istio Request Timeouts, Rate Limiting, FQDN routing, Service Registry GitOps, etc.
I have implemented these mesh configurations for Tier-0 application within my company.