Sidecar proxy pattern in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Sidecar proxy pattern in microservices?

It is a design where a helper component (sidecar) runs alongside a main service to handle tasks like networking, security, and monitoring without changing the main service code.

beginner

Why use a Sidecar proxy instead of embedding features directly in a microservice?

Because it keeps the main service simple and focused, while the sidecar handles cross-cutting concerns like communication, retries, and security independently.

intermediate

Name two common tasks a Sidecar proxy handles in a microservices architecture.

1. Managing network communication between services (like load balancing and retries). 2. Collecting logs and metrics for monitoring.

intermediate

How does the Sidecar proxy pattern improve scalability?

By offloading common tasks to sidecars, each service can scale independently without adding complexity, and sidecars can be updated or scaled separately.

beginner

What is a real-life analogy for the Sidecar proxy pattern?

Like a motorcycle with a sidecar carrying extra tools and supplies, the sidecar proxy carries extra features to support the main service without changing it.

What is the main role of a Sidecar proxy in microservices?

A Replace the main service

B Store the main business logic

C Handle cross-cutting concerns like communication and security

D Manage database transactions

The sidecar proxy handles tasks like communication, security, and monitoring, not the main business logic.

Which of these is NOT a benefit of using the Sidecar proxy pattern?

A Allows independent scaling of features

B Requires rewriting main service for each feature

C Simplifies main service code

D Improves observability

Sidecar proxies avoid rewriting the main service by handling features externally.

In the Sidecar proxy pattern, how are the sidecar and main service typically deployed?

A Sidecar replaces the main service

B On completely separate data centers

C Only the sidecar is deployed, main service runs locally

D Together on the same host or container

Sidecar proxies run alongside the main service, often in the same host or container.

Which scenario best fits using a Sidecar proxy?

A Adding logging to multiple microservices without changing their code

B Building a new monolithic application

C Replacing a database with a cache

D Writing UI components

Sidecar proxies are ideal for adding features like logging without modifying each service.

What is a common technology used to implement Sidecar proxies?

A Envoy proxy

B React framework

C MySQL database

D Dockerfile

Envoy is a popular proxy used as a sidecar in microservices.

Explain the Sidecar proxy pattern and its benefits in microservices architecture.

Think of a helper component that supports the main service without changing it.

Describe a real-world analogy for the Sidecar proxy pattern and why it helps in system design.

Imagine a vehicle with an attached helper compartment.

Practice

1. What is the main purpose of the sidecar proxy pattern in microservices architecture?

easy

A. To handle database transactions directly

B. To replace the main service with a proxy for better performance

C. To store data separately from the main service

D. To add features like communication and security without changing the service code

Solution

1. Step 1: Understand the role of sidecar proxy

   The sidecar proxy runs alongside the main service to add extra features such as communication handling, security, and monitoring.

2. Step 2: Identify what it does not do

   It does not replace the service, store data, or handle database transactions directly.

3. Final Answer:

   To add features like communication and security without changing the service code -> Option D

4. Quick Check:

   Sidecar proxy adds features without changing service code = D [OK]

Hint: Sidecar adds features beside service, not inside it [OK]

Common Mistakes:

• Thinking sidecar replaces the main service
• Confusing sidecar with database or storage
• Assuming sidecar handles business logic

2. Which of the following is the correct way to describe the deployment of a sidecar proxy in a microservices environment?

easy

A. Deployed alongside the main service in the same environment or container

B. Deployed as a separate service on a different server

C. Deployed inside the main service codebase

D. Deployed only on the client side

Solution

1. Step 1: Understand sidecar deployment

   The sidecar proxy runs alongside the main service, usually in the same environment or container, to intercept and manage traffic.

2. Step 2: Eliminate incorrect options

   It is not deployed as a separate service on a different server, nor inside the main service code, nor only on the client side.

3. Final Answer:

   Deployed alongside the main service in the same environment or container -> Option A

4. Quick Check:

   Sidecar runs alongside service = A [OK]

Hint: Sidecar runs side-by-side, not separately or inside code [OK]

Common Mistakes:

• Thinking sidecar is a separate remote service
• Confusing sidecar with code library inside service
• Assuming sidecar runs only on client machines

3. Consider this simplified request flow in a microservice using a sidecar proxy:

Client -> Sidecar Proxy -> Service -> Sidecar Proxy -> Client

What is the main benefit of this flow?

medium

A. The sidecar proxy can handle retries, security checks, and logging without changing the service

B. The service can directly communicate with the client without any proxy

C. The sidecar proxy replaces the service logic for faster processing

D. The client bypasses the sidecar proxy for faster response

Solution

1. Step 1: Analyze the request flow with sidecar proxy

   The sidecar proxy intercepts requests and responses, allowing it to add features like retries, security checks, and logging transparently.

2. Step 2: Understand the benefit of this interception

   This keeps the service code simple and focused on business logic, while the sidecar handles cross-cutting concerns.

3. Final Answer:

   The sidecar proxy can handle retries, security checks, and logging without changing the service -> Option A

4. Quick Check:

   Sidecar manages extra tasks transparently = A [OK]

Hint: Sidecar handles extras, service stays simple [OK]

Common Mistakes:

• Thinking sidecar replaces service logic
• Assuming client talks directly to service
• Believing sidecar slows down response by bypassing

4. A developer notices that the sidecar proxy is not forwarding requests to the main service correctly. Which of the following is the most likely cause?

medium

A. The main service code has a syntax error

B. The client is not sending requests

C. The sidecar proxy configuration is missing the service's local address

D. The database is down

Solution

1. Step 1: Identify sidecar proxy forwarding issue

   If the sidecar proxy does not forward requests, it is often due to incorrect or missing configuration about where the main service is located.

2. Step 2: Rule out unrelated causes

   Syntax errors in service code, client not sending requests, or database issues do not directly cause proxy forwarding failures.

3. Final Answer:

   The sidecar proxy configuration is missing the service's local address -> Option C

4. Quick Check:

   Proxy forwarding fails if service address missing = B [OK]

Hint: Check proxy config for service address first [OK]

Common Mistakes:

• Blaming service code syntax errors
• Assuming client or database issues cause proxy failure
• Ignoring proxy configuration details

5. You want to add monitoring and security features to multiple microservices without changing their code. How does the sidecar proxy pattern help solve this problem at scale?

hard

A. By centralizing monitoring and security in a single proxy for all services

B. By deploying a sidecar proxy with each service instance to handle monitoring and security independently

C. By rewriting each service to include monitoring and security code

D. By removing proxies and letting clients handle monitoring

Solution

1. Step 1: Understand scaling with sidecar proxies

   Deploying a sidecar proxy alongside each service instance allows independent handling of monitoring and security without modifying service code.

2. Step 2: Compare with other options

   Rewriting services is costly and error-prone; centralizing in one proxy creates a bottleneck; removing proxies loses control.

3. Final Answer:

   By deploying a sidecar proxy with each service instance to handle monitoring and security independently -> Option B

4. Quick Check:

   Sidecar per service instance scales features independently = C [OK]

Hint: Sidecar per service instance scales features well [OK]

Common Mistakes:

• Thinking one proxy can handle all services centrally
• Assuming code changes are needed for features
• Ignoring scalability and bottleneck issues