Microservices Service Discovery and Registry 2

Question 1

In client-side service discovery, which component is responsible for selecting a specific service instance to call?

Accepted Answer

The client itself

Answer

In client-side discovery the client queries the registry and applies load-balancing logic to pick an instance.

Question 2

What is the main drawback of client-side service discovery?

Accepted Answer

Discovery logic must be implemented in every client

Answer

Each client must embed discovery and load-balancing logic, often per language/framework.

Question 3

In server-side service discovery, where does the client send its request?

Accepted Answer

To a router or load balancer that queries the registry

Answer

The client calls a router/load balancer, which consults the registry and forwards the request.

Question 4

Which AWS feature is a common example of server-side service discovery?

Accepted Answer

Elastic Load Balancer with target groups

Answer

An ELB routes requests to registered targets without the client knowing instance addresses.

Question 5

A benefit of server-side discovery over client-side discovery is that:

Accepted Answer

Discovery logic is centralized and abstracted from clients

Answer

Centralizing discovery keeps clients simple and language-agnostic.

Microservices Practice Test