Sidecar proxy pattern in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary role of a sidecar proxy in a microservices architecture?

In a microservices system, a sidecar proxy is deployed alongside a service instance. What is its main job?

A To handle service discovery, load balancing, and secure communication for the service it accompanies.

B To replace the main service logic with a proxy implementation.

C To store persistent data for the microservice it is paired with.

D To act as a database caching layer independent of the service.

💡 Hint

Think about what tasks a proxy can do to help a service without changing its core logic.

A sidecar proxy manages networking concerns like routing, load balancing, and security for its paired service, without changing the service code.

❓ Architecture

intermediate

Which diagram best represents the sidecar proxy pattern?

Choose the architecture diagram that correctly shows how a sidecar proxy is deployed with a microservice.

A A proxy embedded inside the service code as a library.

B A proxy server running on a separate host, routing traffic to multiple services remotely.

C A single container running both the service and proxy code in the same process.

D A service container and a proxy container running together on the same host, sharing the network namespace.

💡 Hint

Remember that sidecar proxies run alongside the service but as separate processes or containers.

The sidecar proxy pattern deploys the proxy as a separate container or process next to the service, often sharing the same network environment.

❓ scaling

advanced

How does the sidecar proxy pattern affect scaling of microservices?

When scaling a microservice horizontally, what must be considered about its sidecar proxies?

A A single sidecar proxy can handle all service instances across multiple hosts.

B Each new service instance must have its own sidecar proxy instance to maintain consistent behavior.

C Sidecar proxies are not needed when scaling horizontally because the service handles communication itself.

D Sidecar proxies should be scaled independently from the service instances.

💡 Hint

Think about how sidecar proxies are deployed relative to service instances.

Since sidecar proxies run alongside each service instance, scaling the service means scaling the proxies one-to-one to keep their benefits.

❓ tradeoff

advanced

What is a key tradeoff when using the sidecar proxy pattern?

Using sidecar proxies adds benefits but also some costs. Which option best describes a main tradeoff?

A Simplified deployment but decreased fault tolerance.

B Reduced network latency but loss of security features.

C Improved service communication control at the cost of increased resource usage and complexity.

D Lower resource consumption but limited observability.

💡 Hint

Consider what running extra processes alongside services means for resources and complexity.

Sidecar proxies improve control over communication but require extra CPU, memory, and operational management.

❓ estimation

expert

Estimate the additional resource overhead introduced by sidecar proxies in a microservices deployment with 100 instances.

Each sidecar proxy uses about 50MB memory and 0.1 CPU cores. The service instances use 200MB memory and 0.5 CPU cores each. What is the total additional memory and CPU needed for all sidecar proxies?

A 5GB memory and 10 CPU cores

B 500MB memory and 1 CPU core

C 50GB memory and 100 CPU cores

D 10GB memory and 20 CPU cores

💡 Hint

Multiply the per-instance proxy resource by the number of instances.

100 proxies × 50MB = 5000MB = 5GB memory; 100 proxies × 0.1 CPU = 10 CPU cores total.