Why service mesh manages inter-service traffic in Microservices - Quick Recap

Recall & Review

beginner

What is a service mesh in microservices?

A service mesh is a tool that helps manage how different parts of an app (services) talk to each other. It controls the flow of data between services.

beginner

Why does a service mesh manage inter-service traffic?

It manages traffic to make communication between services safe, reliable, and observable without changing the services themselves.

intermediate

How does a service mesh improve security between services?

It encrypts data between services and controls which services can talk to each other, keeping data safe.

intermediate

What does observability mean in the context of service mesh?

Observability means being able to see and understand how services communicate, helping find and fix problems quickly.

beginner

Name one benefit of using a service mesh for inter-service traffic.

One benefit is automatic retries and load balancing, which helps keep the app working smoothly even if some services are slow or fail.

What is the main role of a service mesh in microservices?

A Deploy services to servers

B Manage communication between services

C Build user interfaces

D Store data for services

A service mesh manages how services communicate with each other, not data storage or UI building.

How does a service mesh improve security between services?

A By encrypting traffic and controlling access

B By speeding up the network hardware

C By storing passwords in plain text

D By disabling service communication

Service mesh encrypts data and controls which services can communicate to keep data safe.

Which feature helps a service mesh handle failures smoothly?

A Disabling traffic monitoring

B Manual restarts of services

C Ignoring failed services

D Automatic retries and load balancing

Automatic retries and load balancing help keep communication smooth even if some services fail.

What does observability in a service mesh allow you to do?

A See and understand service communication

B Hide service errors

C Stop all traffic between services

D Automatically write code

Observability lets you monitor and understand how services talk to each other.

Why is managing inter-service traffic important in microservices?

A To reduce the number of services

B To make services run slower

C To ensure reliable, secure, and observable communication

D To avoid using the network

Managing traffic helps keep communication between services reliable, secure, and easy to monitor.

Explain why a service mesh is used to manage inter-service traffic in microservices.

Think about how services talk safely and smoothly.

Describe the benefits a service mesh provides when managing traffic between microservices.

Focus on what makes service communication better and safer.

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