Going down the Service Mesh rabbit hole — Why do you think you need it, and architecture considerations. This is an effort to help you make better decisions on the topic of The service mesh. You add more production services to your production-grade Kubernetes environment. And things are going well.
Let's start with a good backdrop story.
There comes a time when you have your shiny, new Kubernetes Cluster.
It works, It performs magic, enables you to perform idempotent microservice releases with your CI/CD release model of choice.
Yes, in production.
You have thought through the application load balancers for your Kubernetes (Nginx or any other) ingress controllers, WAF protection, and so on.
Your K8s production microservice (ought to) comes with all the best-practices in place; resource
HorizontalPodAutoscaling, and even
NetworkPolicy to keep SecOps function happy.
This blog post intends to bring both technical and management readers alike to explore the bigger organisational perspective, as well as to appreciate the finer details. _This is _an _effort to help you make _better decisions on the topic of The service mesh.
You add more production services to your production-grade Kubernetes environment. And things are going well.
We should carry out a small candid questionnaire, to ensure we have all angles covered.
Our original Kubernetes tool list was so popular that we've curated another great list of tools to help you improve your functionality with the platform.
In this article, take a look at the service mesh in the microservices world. The software industry has come a long journey and throughout this journey, Software Architecture has evolved a lot. Starting with 1-tier (Single-node), 2-tier (Client/ Server), 3-tier, and Distributed are some of the Software Architectural patterns we saw in this journey.
For teams to monitor, support, and to maintain these services is becoming a challenge so most enterprises have invested in some kind of microservices management tool.
Just as tech is revised and upgraded, so too should a tool comparison be. Service meshes act as the substrate to connect microservices, find the one for you.
Microsoft has released open service mesh (OSM), an alpha service mesh implementation compliant with the SMI specification. OSM covers standard features of a service mesh like canary releases, secure communication, and application insights, similar to other service mesh implementations like Istio, Linkerd, or Consul. Additionally, the OSM team is in the process of donating the project to the CNCF.