Think about service mesh like a routing and tracking service for a package shipped in the mail: it keeps track of the routing rules and dynamically directs the traffic and package route to accelerate delivery and ensure receipt.
In general, service mesh layers on top of your Kubernetes infrastructure and is making communications between services over the network safe and reliable. It does that in a much more graceful and scalable way compared to what would otherwise require a lot of manual, error-prone work and operational burden that is not sustainable in the long-run. Service Mesh manages the network traffic between services.
The thing that is most crucial to understand about microservices is that they are heavily reliant on the network. While Service Mesh technology has been around prior to Kubernetes, the proliferation of microservices that are built on Kubernetes has contributed to the growing interest in Service Mesh solutions.
What is kubernetes microservices how to#
This exponential growth in microservices creates challenges around figuring out how to enforce and standardize things like routing between multiple services/versions, authentication and authorization, encryption, and load balancing within a Kubernetes cluster.īuilding on Service Mesh helps resolve some of these issues, and more. Like the suburbs around a city, the number of small services that are deployed seems to expand exponentially. One outcome that most companies using microservices architecture don’t fully understand the impact of until they are well down the path is microservices sprawl. Increasingly, these containerized applications are Kubernetes-based, as it has become the de-facto standard for container orchestration.
Cloud-native applications are often architected as a constellation of distributed microservices, which are running in Containers.
0 kommentar(er)
