The emerging concept known as Service Mesh, is all about providing an easy abstraction layer for containers and microservices to offload services, and more often than not, networking.
Among the many vendors in the space is Containous, which has been building and leading the open-source Traefik reverse proxy effort. On Sept. 4, Containous announced the Maesh service mesh effort as an attempt at a more lightweight and simpler service mesh. Maesh will face some stiff competition in service mesh space, with multiple commercial efforts underway, most of which are underpinned by the open source Istio service mesh project.
“Maesh is a simple, yet full-featured service mesh. It is container-native and fits as your de-facto service mesh in your Kubernetes cluster,” the Maesh GitHub project page states. “Moreover, Maesh is opt-in by default, which means that your existing services are unaffected until you decide to add them to the mesh.”
With some service mesh approaches there is a need for what is known as a sidecar container, that is a docker container that sits next to a Kubernetes pod. With Maesh, the routing is handled via proxy endpoints running on each node.
Maesh makes use of CoreDNS, which is a Cloud Native Computing Foundation (CNCF) project that is the default DNS provider for Kubernetes.
Containous developer Damien Duportal explained that the use of CoreDNS, allows users to use the Maesh endpoints instead of the standard Kubernetes service endpoints to benefit from the Maesh feature set.
“Maesh endpoints run side-by-side with user services: you choose whether you use them or not (opt-in),” Duportal wrote. ” This gives more confidence, since users know that they are able to test, and revert back to the user services: they should be happy with the result.”
Sean Michael Kerner is a senior editor at EnterpriseNetworkingPlanet and InternetNews.com. Follow him on Twitter @TechJournalist.