DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Please enter at least three characters to search
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Zones

Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

The software you build is only as secure as the code that powers it. Learn how malicious code creeps into your software supply chain.

Apache Cassandra combines the benefits of major NoSQL databases to support data management needs not covered by traditional RDBMS vendors.

Generative AI has transformed nearly every industry. How can you leverage GenAI to improve your productivity and efficiency?

Modernize your data layer. Learn how to design cloud-native database architectures to meet the evolving demands of AI and GenAI workloads.

Related

  • Curating Efficient Distributed Application Runtime (Dapr) Workflows
  • Mastering System Design: A Comprehensive Guide to System Scaling for Millions (Part 1)
  • 5 Ways a Service Mesh Can Better Manage App Data Sharing
  • Scatter-Gather Pattern

Trending

  • Scaling Microservices With Docker and Kubernetes on Production
  • Build a Simple REST API Using Python Flask and SQLite (With Tests)
  • Event Driven Architecture (EDA) - Optimizer or Complicator
  • How To Introduce a New API Quickly Using Quarkus and ChatGPT
  1. DZone
  2. Data Engineering
  3. Data
  4. Istio Service Mesh Data Plane

Istio Service Mesh Data Plane

In this post, we take a look into the Istio Service Mesh Data Plane and its functionalities within Istio's architecture.

By 
Samir Behara user avatar
Samir Behara
DZone Core CORE ·
Jun. 07, 19 · Analysis
Likes (5)
Comment
Save
Tweet
Share
12.3K Views

Join the DZone community and get the full member experience.

Join For Free

As enterprises transition from a monolithic to microservices architecture, they have found it difficult to manage the service to service communication and handle functionalities such as security, traffic control, resiliency, monitoring, metrics, and logging. More requirements like A/B testing, canary releases, rate limiting, policy enforcement, access control, and end-to-end authentication become another burden. Istio solves such complex requirements while not requiring changes to application code.

A service mesh allows applications to offload these capabilities from application-level libraries to a separate infrastructure layer and allow developers to focus on the business logic itself. Istio is one of the best implementations of a service mesh.

In my last blog, we looked at Istio Control Plane components — Galley, Pilot, Mixer, and Citadel. We also discussed the responsibilities of the Istio Control Plane which is primarily the administration and configuration of the Sidecar Proxies to enforce policies and collect telemetry - Istio Service Mesh Control Plane.

In this blog post, I will explain the Istio Service Mesh Data Plane and its functionalities.

Istio Architecture 

Inside a service mesh, we have the concept of a Data Plane and Control Plane:

  • The Control Plane responsibility is to manage and configure the sidecar proxies to enforce policies and collect telemetry.
  • The Data Plane responsibility is to handle the communication between the services and take care of the functionalities like Service Discovery, Load Balancing, Traffic Management, Health Check, etc.

Istio Architecture

Istio Data Plane

The Istio Data Plane is primarily comprised of the Envoy proxies which are attached as dedicated sidecars to each application instance.

Istio Data Plane intercepts all incoming (ingress) and outgoing (egress) network traffic. This provides you the ability to apply all these required functionalities mentioned below at this separate infrastructure layer, without polluting the application code.

The data plane is composed of a set of intelligent proxies (Envoy) deployed as sidecars. Primary Responsibilities of the Sidecar Proxy: 
Service Discovery, Load Balancing, Authentication and Authorization, Request Tracing, Traffic Management, Fault Injection, Rate Limiting, Observability

Istio Data Plane with Envoy Sidecar

The diagram above shows how Envoy as a Sidecar Container makes the Service lightweight and compact, in the process handling all the service to service communication.

Each pod inside the service mesh must be running an Istio compatible sidecar. You can inject an Istio sidecar into a pod manually using the istioctl CLI tool or automatically using the Istio sidecar injector.

Benefits of Sidecar Implementation 

  • Separation of configuration code and Business functionalities ensures loose coupling and clear segregation of responsibilities.
  • The configuration code is handled by a dedicated infrastructure layer and not diluted into the application code.
  • Envoy proxies provide a standardized implementation of functionalities in a polyglot landscape.
  • No application-level code changes are required to implement the service to service communication inside the service mesh.

To summarize this blog post, here are the primary differences between the Istio Data Plane and Istio Control Plane:

  • The Data Plane touches every packet/request in the system, whereas the Control Plane does not.
  • The Data Plane is responsible for service discovery, load balancing, traffic management, authentication, observability whereas the Control Plane configures the sidecar proxies to enforce policies and collect telemetry.

Additional Istio Resources for reference -

  • Introducing Istio Service Mesh for Microservices

  • Service mesh data plane vs. control plane

microservice Data (computing)

Published at DZone with permission of Samir Behara, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Curating Efficient Distributed Application Runtime (Dapr) Workflows
  • Mastering System Design: A Comprehensive Guide to System Scaling for Millions (Part 1)
  • 5 Ways a Service Mesh Can Better Manage App Data Sharing
  • Scatter-Gather Pattern

Partner Resources

×

Comments
Oops! Something Went Wrong

The likes didn't load as expected. Please refresh the page and try again.

ABOUT US

  • About DZone
  • Support and feedback
  • Community research
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • support@dzone.com

Let's be friends:

Likes
There are no likes...yet! 👀
Be the first to like this post!
It looks like you're not logged in.
Sign in to see who liked this post!