[Service Mesh] Istio vs Envoy

Each Microservice that constitutes the Microservice architecture identifies each service for communication between Microservices, identifies routes, performs load balancing, and serves as a circuit break for the entire service. It is Service Mesh that integrates these functions into a single layer.


Istio is an open-source solution for implementing Service Mesh (Service Mesh) developed by IBM, Redhat, VMware, and Google. Istio distributes Envoy, a proxy that can communicate all networks between microservices, to microservices in a sidecar pattern, stores and manages/supervises the settings of proxies and serves as a controller to deliver the settings to proxies.


  • Istio Architecture

Istio is divided into Data Plan and Control Plan, and each architecture is shown in the figure below.


  • Mesh-Agnostic Code (istio/envoy) vs Mesh-Aware Code(Eureka) Architecture

The two most commonly used methods of configuring Service Mesh, Mesh-Agnostic Code (istio/envoy) using Proxy as a Sidecar format, and Mesh-Aware Code, such as Spring Cloud Eureka, can be compared architecturally using the figure below.

                            Mesh-Agnostic Code (istio/envoy) -MSA Service Mesh

                            Mesh-Aware Code(Eureka)- Service Mesh



reference: https://www.freecodecamp.org/news/jhipster-microservices-with-istio-service-mesh-on-kubernetes-a7d0158ba9a3/

Comments

Popular posts from this blog

[Kubernetes] Node Overcommitted

[AWS] What is the Cloud Formation?

How to Install jenkins using Helm chart on instance