Service discovery concept in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary role of service discovery in microservices?

In a microservices architecture, what is the main purpose of service discovery?

A To manage user authentication and authorization

B To store user data securely in a database

C To monitor the health of a single service only

D To enable services to find and communicate with each other dynamically without hardcoding addresses

💡 Hint

Think about how services know where to send requests when their locations can change.

Service discovery allows microservices to locate each other dynamically, avoiding hardcoded IPs or ports, which can change due to scaling or failures.

❓ Architecture

intermediate

Which component typically acts as the service registry in service discovery?

In a microservices system, which component is responsible for keeping track of all available service instances?

A Service registry

B API gateway

C Database

D Load balancer

💡 Hint

This component holds the list of active services and their locations.

The service registry maintains a dynamic list of service instances and their network locations, enabling service discovery.

❓ scaling

advanced

How does service discovery help when scaling microservices horizontally?

When multiple instances of a microservice are added to handle more load, how does service discovery assist?

A It requires manual configuration of each new instance's address

B It duplicates the database to match the number of instances

C It automatically updates the registry with new instances so clients can find them without manual changes

D It disables older instances to avoid conflicts

💡 Hint

Think about how new service instances become discoverable without manual intervention.

Service discovery updates the registry dynamically as new instances start or stop, allowing clients to find all available instances automatically.

❓ tradeoff

advanced

What is a tradeoff of using client-side service discovery compared to server-side?

Client-side and server-side service discovery are two common patterns. What is a key tradeoff when using client-side discovery?

A Clients handle more complexity but reduce load on central components

B Clients have less control over routing decisions

C It requires no service registry at all

D It eliminates the need for load balancing

💡 Hint

Consider who manages the discovery logic and the impact on system components.

Client-side discovery pushes the responsibility to clients, increasing their complexity but reducing dependency on central servers, which can improve scalability.

❓ estimation

expert

Estimate the number of service registry updates per minute in a system with 100 microservice instances, each registering every 30 seconds.

Assuming each of the 100 microservice instances sends a heartbeat or registration update every 30 seconds, how many updates does the service registry receive per minute?

A 100 updates per minute

B 200 updates per minute

C 50 updates per minute

D 300 updates per minute

💡 Hint

Calculate how many updates each instance sends per minute and multiply by the number of instances.

Each instance sends 2 updates per minute (60/30). With 100 instances, total updates = 100 * 2 = 200 per minute.

Practice

1. What is the main purpose of service discovery in a microservices architecture?

easy

A. To help services find and communicate with each other automatically

B. To store user data securely

C. To manage database transactions

D. To handle user authentication

Solution

1. Step 1: Understand the role of service discovery

   Service discovery allows microservices to locate each other dynamically without hardcoding addresses.

2. Step 2: Identify the correct purpose

   It is not about data storage, transactions, or authentication but about service communication.

3. Final Answer:

   To help services find and communicate with each other automatically -> Option A

4. Quick Check:

   Service discovery = automatic service location [OK]

Hint: Service discovery = finding services automatically [OK]

Common Mistakes:

• Confusing service discovery with data storage
• Thinking it manages user authentication
• Assuming it handles database transactions

2. Which of the following is a common component used in service discovery for microservices?

easy

A. Load balancer

B. Service registry

C. API gateway

D. Database shard

Solution

1. Step 1: Identify components related to service discovery

   A service registry keeps track of available service instances and their locations.

2. Step 2: Differentiate from other components

   Load balancers distribute traffic, API gateways manage requests, and database shards split data, but none perform service discovery.

3. Final Answer:

   Service registry -> Option B

4. Quick Check:

   Service registry = key for service discovery [OK]

Hint: Service registry stores service locations [OK]

Common Mistakes:

• Confusing load balancer with service registry
• Mixing API gateway with service discovery
• Thinking database shards help find services

3. Consider this simplified service discovery flow:

1. Service A queries the registry for Service B's address.
2. Registry returns Service B's current IP and port.
3. Service A connects to Service B using the returned address.
4. Service B processes the request and responds.

What happens if Service B changes its IP but the registry is not updated?

medium

A. Service B will notify Service A directly

B. Service A will automatically find the new IP

C. The registry will redirect Service A to the new IP

D. Service A will connect to the old IP and fail

Solution

1. Step 1: Analyze the flow when registry is outdated

   If the registry has an old IP, Service A uses that wrong address to connect.

2. Step 2: Understand consequences of stale registry data

   Service A cannot find Service B at the old IP, so connection fails; no automatic update or redirection occurs.

3. Final Answer:

   Service A will connect to the old IP and fail -> Option D

4. Quick Check:

   Stale registry = failed connection [OK]

Hint: Outdated registry causes failed connections [OK]

Common Mistakes:

• Assuming automatic IP update without registry refresh
• Thinking services notify each other directly
• Believing registry redirects requests automatically

4. A developer notices that service discovery is failing because services cannot find each other. The registry is running, but services do not register themselves. What is the most likely cause?

medium

A. The registry database is full

B. Network latency is too high

C. Services are not sending heartbeat or registration requests to the registry

D. Services are using incorrect API versions

Solution

1. Step 1: Identify why services are missing in registry

   Services must actively register or send heartbeats to the registry to be discoverable.

2. Step 2: Eliminate other causes

   Full database or network latency might cause delays but not complete absence; API version mismatch affects communication, not registration.

3. Final Answer:

   Services are not sending heartbeat or registration requests to the registry -> Option C

4. Quick Check:

   Missing registration = discovery failure [OK]

Hint: Services must register to be discoverable [OK]

Common Mistakes:

• Blaming network latency for missing registrations
• Assuming registry storage limits cause missing services
• Confusing API version issues with registration problems

5. In a large microservices system with many instances starting and stopping frequently, which service discovery approach best supports scalability and fault tolerance?

hard

A. Using a centralized service registry with periodic health checks and automatic deregistration

B. Hardcoding service IPs in each microservice configuration

C. Using DNS-based service discovery without health checks

D. Relying on client-side caching of service addresses without updates

Solution

1. Step 1: Evaluate scalability and fault tolerance needs

   Frequent changes require dynamic updates and health checks to avoid stale info and failures.

2. Step 2: Compare approaches

   Centralized registry with health checks keeps accurate service info; hardcoding or caching causes stale data; DNS without health checks misses failures.

3. Final Answer:

   Using a centralized service registry with periodic health checks and automatic deregistration -> Option A

4. Quick Check:

   Dynamic registry + health checks = scalable, fault tolerant [OK]

Hint: Dynamic registry with health checks scales best [OK]

Common Mistakes:

• Hardcoding IPs causing poor scalability
• Ignoring health checks leading to stale data
• Relying on caching without updates