Linkerd overview in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary role of Linkerd in a microservices architecture?

Linkerd is a service mesh used in microservices. What is its main function?

A It replaces the need for load balancers in the network.

B It stores data persistently for microservices to access.

C It acts as a database query optimizer for microservices.

D It manages communication between microservices by providing observability, reliability, and security.

💡 Hint

Think about what a service mesh does for microservices communication.

Linkerd provides a transparent layer that manages service-to-service communication, adding features like retries, timeouts, and security without changing the services themselves.

❓ Architecture

intermediate

Which component in Linkerd handles the proxying of network traffic between services?

In Linkerd's architecture, which part is responsible for intercepting and managing the network traffic between microservices?

A Service Registry

B Control Plane

C Data Plane Proxy (sidecar proxy)

D API Gateway

💡 Hint

This component runs alongside each service instance.

The Data Plane Proxy, often a sidecar proxy, runs next to each service instance and intercepts all network traffic to provide features like load balancing and retries.

❓ scaling

advanced

How does Linkerd ensure scalability when managing thousands of microservices?

Linkerd must handle communication for many microservices. Which design aspect helps it scale efficiently?

A Storing all service data in a single database

B Distributed sidecar proxies running alongside each service instance

C Using a single monolithic control plane to manage all services

D Centralized proxy for all traffic to reduce overhead

💡 Hint

Think about how distributing work helps scale systems.

Linkerd uses sidecar proxies deployed with each service instance, distributing the load and avoiding bottlenecks, which allows it to scale horizontally.

❓ tradeoff

advanced

What is a tradeoff when using Linkerd's sidecar proxy model in microservices?

Using sidecar proxies adds benefits but also some costs. Which is a common tradeoff?

A Increased network latency due to extra proxy hops

B Elimination of the need for service discovery

C Simplified deployment with no additional resource use

D Reduced security because proxies bypass encryption

💡 Hint

Adding a proxy means traffic passes through an extra step.

Sidecar proxies add an extra network hop for each request, which can slightly increase latency and resource consumption.

❓ estimation

expert

Estimate the additional CPU overhead per service instance when deploying Linkerd sidecar proxies at scale.

If each Linkerd sidecar proxy adds approximately 5% CPU overhead to a service instance, what is the total CPU overhead for 1000 instances running on identical hardware?

A 5000% total CPU overhead across all instances

B 5% total CPU overhead across all instances

C 50% total CPU overhead across all instances

D 100% total CPU overhead across all instances

💡 Hint

Multiply the overhead per instance by the number of instances.

Each instance adds 5% CPU overhead. For 1000 instances, total overhead is 5% * 1000 = 5000%. This means the sum of overhead across all instances is 50 times the CPU of one instance.