There are a couple of choices for leveraging the service mesh solutions. A service mesh solution can be presented as a library so that any microservices-centric application can import and use it on demand. We are used to import programming language packages, libraries, and classes in a typical application building and execution. Libraries such as Hystrix and Ribbon are well-known examples of this approach. This works well for applications that are exclusively written in one language.
There is a limited adoption of this library approach as microservicecs-centric applications are being coded using different languages. There are other approaches too, which are explained as follows:
Node agent: In this architecture, there is a separate agent running on every node. This setup can service a heterogeneous mix of workloads. It is just the opposite of the library model. Linkerd's recommended deployment in Kubernetes works like this. F5's Application Service Proxy (ASP) and...