Source: thenewstack.io
KubeCon CloudNativeCon: Service Mesh Battle Stories and FixesCategory: Software, Business, Kubernetes, automation, yaml
Honeycomb is sponsoring The New Stack’s coverage of Kubecon+CloudNativeCon North America 2020. There’s a lot to say about each of these service meshes and how they work: their architecture, why they’re made, what they’re focused on, what they do when they came about and why some of them aren’t here anymore and why we’re still seeing new ones,” Lee Calcote, founder of Layer5, explained during his talk with Kush Trivedi, a Layer5 maintainer, entitled “Service Mesh Specifications and Why They Matter in Your Deployment.”
One-third of the respondents in The New Stack survey of our readers said their organizations already use service mesh.
Service mesh has been compared to DNS in reverse in that DNS offers a vertical-like check of network traffic, while the service mesh extends laterally to ensure continuity between the different services and sidecars within a cluster.
Organizations will likely look to use at least more than one API service layer and service mesh for their clusters.
One-third of the respondents in The New Stack survey of our readers said their organizations already use service mesh.
Service mesh has been compared to DNS in reverse in that DNS offers a vertical-like check of network traffic, while the service mesh extends laterally to ensure continuity between the different services and sidecars within a cluster.
Organizations will likely look to use at least more than one API service layer and service mesh for their clusters.
Related Articles
Community Partners
DevOps Careers