Service Mesh as an API Management

By in

what is a Service Mesh?

The concept of service mesh has recently become more popular and the idea is to observability, the security and reliability features of the API Management Platform rather than the services. This is an abstraction technique for solving the complexity of API Management issues.

Why has the Service Mesh become more popular? Well, recently the containerised deployment, for example, Kubernetes, is advocating for this approach as a part of the cloud-native adoption process.

In this space, there are two projects to watch Istio and Linkerd. the pattern in question is called Sidecar, where a bunch of proxies are deployed along with the application (microservices). The role of these sidecar proxies is to facilitate the communication between the microservices., the control is done at a layer, called the control plane where the management of data flow on the data plate is done.

The Cloud-native applications usually consist of numerous microservices which are interlinked, each service might have multiple instances managed and controlled by Kubernetes. The challenge here is to provide a reliable and secure end-to-end performance for the intra-service communication within the service network, or the application network as referred by MuleSoft.

Products to Look

  • MuleSoft API Management
  • Zule ( Sprintboot)
  • Linkered

Service Mesh and Kubernetes
In another article, I am going to talk about this topic in more detail. Stay tuned!

author: Pooyan Farahani, Data Integration Architect for financial services.

(0 votes. Average 0 of 5)
Leave a reply

Your email address will not be published. Required fields are marked *