Elastic Service Mesh

<< Back to Technical Glossary

Elastic Service Mesh Definition

An elastic service mesh provides traffic management for containerized applications with a microservices architecture. It also provides high level application services such as load balancing, monitoring and security.

Diagram depicts an elastic service mesh for managing multiple container clusters of web application servers.

FAQs

What Is an Elastic Service Mesh?

An elastic service mesh gives organizations a flexible framework for an array of network services. It works alongside containers and manages services by removing the operational complexity associated with modern microservices applications. The service mesh forms a fabric connecting each container and microservice so they can communicate and interoperate securely.

Why Use an Elastic Service Mesh?

An elastic service mesh provides the following benefits:

• Global and local traffic management — An array of network service proxies on each node in the container cluster serves as a gateway between containers and servers.

• Application monitoring and analytics — Collects, aggregates, accumulates and stores metrics and logs for containerized applications.

• Dynamic service discovery — Bridges the gap between a service’s name and access information (IP address) by providing dynamic mapping.

How Is Elastic Service Mesh Used In Container Networking?

Elastic service mesh is orchestrated by container networking platforms like Kubernetes. Interactions are visualized in an application map.

Elastic service mesh implementation provides a modern, distributed application services platform for containerized applications based on microservices architecture. Those application services include load balancing, health checks, as well as Transport Layer Security (TLS) and Secure Sockets Layer (SSL) offload. Elastic service mesh is a critical component because container clusters can have thousands of containers, which cannot be manually managed. The Kubernetes clusters require full automation and policy-driven deployments.

How Does An Elastic Service Mesh Work?

An elastic service mesh architecture is made of proxies that serve as gateways to each interaction that occurs between containers. The proxy accepts the connection and spreads the load across the service mesh. Therefore, the concept of a “mesh” looks like an illustration of the many connections because they create a woven microservice service mesh.

A central controller for service mesh integrates with the Kubernetes platform, which is an open source system for automating the deployment and management of containerized applications. For example, Istio and Envoy are open source projects that help to deliver service mesh capabilities for the Kubernetes environment. The central control plane (Istio) orchestrates the connections and tells the proxies (Envoy instances) deployed alongside containers to implement access control and collect performance metrics.

Does Avi Offer An Elastic Service Mesh?

Yes, the Avi Vantage Platform delivers an Universal Service Mesh for container-based microservices applications as well as traditional applications. The Avi Vantage Platform delivers multi-cloud application services such as load balancing, monitoring and security for containerized applications with microservices architecture through dynamic service discovery, application maps, and micro-segmentation. The platform is an elastic service mesh which is optimized for North-South (inbound and outbound) and East-West (usually within the datacenter) traffic management, including local and global load balancing. Avi integrates with OpenShift / Kubernetes for container orchestration and security,and Istio service mesh.

For more information see the following elastic service mesh resources: