0
0
Microservicessystem_design~12 mins

Service mesh concept in Microservices - Architecture Diagram

Choose your learning style9 modes available
LearnWhyDeepArchPracticeChallengeDesignRecallScale
System Overview - Service mesh concept

A service mesh manages communication between microservices in a distributed system. It provides features like secure connections, traffic control, and observability without changing the microservices themselves.

Key requirements include reliable service-to-service communication, security, and easy monitoring.

Architecture Diagram
User
  |
  v
Load Balancer
  |
  v
API Gateway
  |
  v
+-------------------+       +-------------------+
|  Service A        |<----->|  Service B        |
|  (with sidecar)   |       |  (with sidecar)   |
+-------------------+       +-------------------+
        |                           |
        v                           v
   Service Mesh Control Plane (manages sidecars, policies, telemetry)
        |
        v
   Monitoring & Logging System
Components
User
client
Initiates requests to the system
Load Balancer
load_balancer
Distributes incoming requests evenly to API Gateway instances
API Gateway
api_gateway
Entry point for client requests, routes to appropriate services
Service A
service
Business logic microservice with sidecar proxy
Service B
service
Another business logic microservice with sidecar proxy
Sidecar Proxy
proxy
Handles service-to-service communication, security, and telemetry for each service
Service Mesh Control Plane
control_plane
Manages configuration, policies, and telemetry collection for sidecars
Monitoring & Logging System
monitoring
Collects and displays metrics and logs from the mesh
Request Flow - 13 Hops
User → Load Balancer
Load Balancer → API Gateway
API Gateway → Service A Sidecar Proxy
Service A Sidecar Proxy → Service A
Service A Sidecar Proxy → Service B Sidecar Proxy
Service B Sidecar Proxy → Service B
Service B Sidecar Proxy → Service A Sidecar Proxy
Service A → Service A Sidecar Proxy
Service A Sidecar Proxy → API Gateway
API Gateway → Load Balancer
Load Balancer → User
Sidecar Proxies → Service Mesh Control Plane
Service Mesh Control Plane → Monitoring & Logging System
Failure Scenario
Component Fails:Service Mesh Control Plane
Impact:Sidecar proxies cannot receive updated policies or configurations, but existing connections continue working. Telemetry collection pauses.
Mitigation:Sidecars cache last known config and continue operating. Control plane is deployed with replicas for high availability.
Architecture Quiz - 3 Questions
Test your understanding
Which component manages communication policies between microservices?
AService Mesh Control Plane
BAPI Gateway
CLoad Balancer
DMonitoring & Logging System
Design Principle
This architecture shows how a service mesh uses sidecar proxies alongside microservices to manage secure, observable, and reliable communication without changing the services themselves. The control plane centralizes configuration and telemetry, enabling dynamic policy enforcement and monitoring.