Why service mesh manages inter-service traffic in Microservices - Architecture Impact

System Overview - Why service mesh manages inter-service traffic

A service mesh helps microservices communicate securely and reliably. It manages how services talk to each other, handling traffic routing, retries, and security without changing the services themselves.

Architecture Diagram

User
  |
  v
Load Balancer
  |
  v
API Gateway
  |
  v
+-------------------+
|   Service Mesh     |
| +---------------+ |
| | Sidecar Proxy |<-----> Service B
| +---------------+ |
|        |          |
|        v          |
|   Service A       |
+-------------------+
        |
        v
   Database

Components

User

user

Initiates requests to the system

Load Balancer

load_balancer

Distributes incoming traffic evenly across API gateways

API Gateway

api_gateway

Entry point for client requests, routes to services

Service Mesh

service_mesh

Manages inter-service communication, traffic routing, retries, and security

Sidecar Proxy

proxy

Runs alongside each service to intercept and manage traffic

Service A

service

Business logic service that communicates with other services

Service B

service

Another business logic service communicating with Service A

Database

database

Stores persistent data for services

Request Flow - 9 Hops

User → Load Balancer

Load Balancer → API Gateway

API Gateway → Service Mesh (Sidecar Proxy of Service A)

Sidecar Proxy of Service A → Sidecar Proxy of Service B

Service B → Database

Database → Service B

Sidecar Proxy of Service B → Sidecar Proxy of Service A

Service A → API Gateway

API Gateway → User

Failure Scenario

Component Fails:Sidecar Proxy of Service A

Impact:Service A cannot send or receive inter-service traffic, causing failures in communication with Service B and degraded functionality

Mitigation:Service mesh retries requests, fallback to circuit breaker patterns, and alerting for quick recovery; sidecar proxies are restarted automatically by orchestration

Architecture Quiz - 3 Questions

What component manages retries and security between services?

A Sidecar Proxy

B Load Balancer

C Database

D User

Design Principle

Using a service mesh with sidecar proxies separates communication logic from business logic. This allows centralized control of traffic, retries, and security without changing service code, improving reliability and observability.

Practice

1. Why does a service mesh manage inter-service traffic in a microservices architecture?

easy

A. To improve security, reliability, and observability between services

B. To replace the need for a database in microservices

C. To write the business logic inside each service

D. To increase the size of each service for better performance

Solution

1. Step 1: Understand the role of service mesh

   A service mesh controls how services communicate, focusing on security, reliability, and monitoring.

2. Step 2: Identify what service mesh does not do

   It does not replace databases or add business logic; it manages traffic between services.

3. Final Answer:

   To improve security, reliability, and observability between services -> Option A

4. Quick Check:

   Service mesh manages traffic for security and reliability = A [OK]

Hint: Service mesh controls communication, not business logic or storage [OK]

Common Mistakes:

• Thinking service mesh replaces databases
• Confusing service mesh with application code
• Assuming service mesh increases service size

2. Which syntax correctly describes how a service mesh uses sidecar proxies?

easy

A. database -> service -> sidecar proxy

B. service -> sidecar proxy -> other service

C. sidecar proxy -> service -> database

D. service <- database <- sidecar proxy

Solution

1. Step 1: Understand sidecar proxy role

   Sidecar proxies sit alongside services to intercept and manage traffic between services.

2. Step 2: Identify correct traffic flow

   Traffic flows from the service through its sidecar proxy to the other service.

3. Final Answer:

   service -> sidecar proxy -> other service -> Option B

4. Quick Check:

   Sidecar proxies manage traffic between services = D [OK]

Hint: Sidecar proxies sit next to services, managing outgoing traffic [OK]

Common Mistakes:

• Confusing database direction with sidecar proxy
• Reversing traffic flow arrows
• Mixing service and database roles

3. Given this simplified service mesh setup, what is the expected behavior when Service A calls Service B and Service B is temporarily down?

Service A -> Sidecar Proxy A -> Sidecar Proxy B -> Service B

Options:

medium

A. The call fails immediately with no retries

B. Service A handles retries without sidecar involvement

C. Sidecar Proxy A retries the call automatically before failing

D. Sidecar Proxy B forwards the call to a database instead

Solution

1. Step 1: Recognize retry feature in service mesh

   Service mesh sidecar proxies can automatically retry failed calls to improve reliability.

2. Step 2: Identify which proxy handles retries

   Sidecar Proxy A, managing outgoing traffic from Service A, retries the call before reporting failure.

3. Final Answer:

   Sidecar Proxy A retries the call automatically before failing -> Option C

4. Quick Check:

   Sidecar proxies handle retries to improve reliability = B [OK]

Hint: Sidecar proxies retry failed calls automatically [OK]

Common Mistakes:

• Assuming no retries happen
• Thinking service code retries instead
• Confusing proxy roles with database

4. You configured a service mesh but notice that traffic between services is not encrypted. What is the most likely cause?

medium

A. Service mesh does not support encryption

B. Services are using HTTP instead of HTTPS internally

C. The database connection is not encrypted

D. Sidecar proxies are not enabled to handle TLS encryption

Solution

1. Step 1: Understand encryption in service mesh

   Service mesh uses sidecar proxies to encrypt traffic between services using TLS.

2. Step 2: Identify common misconfiguration

   If sidecar proxies are not configured or enabled for TLS, traffic remains unencrypted.

3. Final Answer:

   Sidecar proxies are not enabled to handle TLS encryption -> Option D

4. Quick Check:

   Encryption depends on sidecar proxy TLS setup = A [OK]

Hint: Check sidecar proxy TLS settings for encryption issues [OK]

Common Mistakes:

• Blaming service internal HTTP usage
• Confusing database encryption with service traffic
• Assuming service mesh lacks encryption feature

5. In a microservices system using a service mesh, how does the mesh help when one service experiences intermittent failures?

hard

A. It automatically retries requests, routes around failures, and collects metrics for monitoring

B. It stops all traffic to the failing service until manually restarted

C. It merges the failing service into other services to avoid downtime

D. It disables sidecar proxies to reduce overhead during failures

Solution

1. Step 1: Identify service mesh features for failure handling

   Service mesh retries requests, performs circuit breaking (routing around failures), and gathers metrics.

2. Step 2: Understand what service mesh does not do

   It does not stop all traffic, merge services, or disable proxies during failures.

3. Final Answer:

   It automatically retries requests, routes around failures, and collects metrics for monitoring -> Option A

4. Quick Check:

   Service mesh improves reliability with retries and monitoring = C [OK]

Hint: Service mesh retries and monitors to handle failures smoothly [OK]

Common Mistakes:

• Thinking mesh stops traffic completely
• Believing mesh merges services automatically
• Assuming proxies are disabled on failure