“Service mesh “— the Nervous system of Microservices

A Service mesh is a software layer that decouples the communication between Microservices.

You can compare Service mesh to TCP stack. Soon, Service mesh will be an integral part of Microservices project.

Every Microservice will not talk to each other directly. Microservices will talk only with Service mesh service.

We have two leading Service mesh tools — Linkerd and Envoy. We can integrate Service mesh tools with Orchestration tools — Kubernetes and Mesos.

Past few months, Linkerd is used in making more than 100 Billion requests.

Microservices ecosystem requirements:

  • Load balancing
  • Path based routing — L7 intelligent proxy
  • Auto Service discovery
  • Resilience
  • 100% Uptime
  • Monitoring & Metrics
  • Distributed Tracing
  • Encryption
  • Circuit breaker, Retries, Rate limiting
  • supports: REST & gRPC protocols

In Traditional apps, the App developer has to worry about these features and code the [Communication & Networking] logic into their Apps.

But now, we can get all these Features out of the box by using Service mesh.

Linkerd Dashboard: