Service mesh in 2 minute

What is Service Mesh

One of the popular Microservice Architecture patterns, another one is API Gateway.

In this pattern, services are communicating with each other (almost) directly without any gateway.

Patterns of Service Mesh

• The library?that your microservices applications import and use.
• The Node Agent?or daemon services all of the containers on a particular node/machine.
• The Sidecar?communication with other services is handled by a coexisting daemon service.

Few lines on each pattern

The library: as simple as you are importing a jar/ package in your project code. Works best if you are developing the code with the same coding language as your library.

The Node Agent: in this model, the other service will coexist in the same node with your service. AppDynamic agent / Splunk agent can be considered as an analogy to understand this pattern.

The Sidecar: Your service should only focus on the business logic execution where all the outer world communication has been taken care of (proxy) through the daemon service. The best practice suggests the Service-Daemon communication over IPC (Inter-process communication).

IPC takes place when Service uses localhost:// or IPloopback (127.0.0.1)