Learn the vocabulary of looking up a service's current location instead of hardcoding it.
0 / 5 completed
1 / 5
At standup, a dev mentions services looking up another service's current network location from a shared registry at request time, rather than a hardcoded IP address baked into configuration. What is this mechanism called?
Service discovery has services look up another service's current network location from a shared registry at request time, rather than depending on a hardcoded IP address baked into static configuration that quickly goes stale as instances are added, removed, or rescheduled. Load balancing distributes traffic across a set of instances that are already known, which assumes the discovery problem has already been solved. This dynamic lookup is what makes a system resilient to instances changing location constantly, which is the norm in a container-orchestrated or auto-scaled environment.
2 / 5
During a design review, the team compares a client directly querying the registry itself to find a healthy instance, versus a client simply calling a fixed address and letting a server-side proxy handle the lookup. What does the second approach represent?
This is server-side service discovery, where the lookup and routing complexity lives behind a proxy instead of being duplicated inside every client, so a client only ever needs to know one fixed address. Client-side service discovery instead requires every client to implement its own registry-lookup logic directly. This split is a genuine architectural choice, trading off where the discovery complexity lives and how much logic every individual client needs to carry.
3 / 5
In a code review, a dev notices a service registering itself with the discovery registry on startup and explicitly deregistering itself as part of its shutdown sequence, rather than just disappearing when the process exits. What does this represent?
This is registry lifecycle hygiene ensuring a terminated instance is promptly removed from the pool of routable instances, rather than lingering in the registry as a stale, dead entry that other services might still be routed to. A read replica describes an unrelated database deployment pattern. Explicit deregistration on shutdown, paired with health checks that catch an instance that dies unexpectedly without deregistering cleanly, is what keeps the registry an accurate, trustworthy source of truth.
4 / 5
An incident report shows requests kept being routed to an instance that had already been terminated during a scale-down, because the registry still listed it and no health check had caught the stale entry. What practice would prevent this?
Combining prompt deregistration on shutdown with active health checks ensures the registry removes a stale entry even if the explicit deregistration step is ever missed, for instance because the instance crashed abruptly rather than shutting down gracefully. Relying solely on explicit deregistration, with no health check as a backstop, is exactly what let requests keep routing to an already-terminated instance in this incident. This combination of graceful deregistration and active health checking is the standard defense against a stale registry entry.
5 / 5
During a PR review, a teammate asks why the team adopts dynamic service discovery instead of just hardcoding each service's IP address in configuration, which is simpler to reason about. What is the reasoning?
A hardcoded IP address goes stale the moment an instance is rescheduled, scaled, or replaced, which happens routinely in a container-orchestrated or auto-scaled environment, leaving every client with an outdated location the instant that happens. A dynamic registry keeps every client's view of a service's location current automatically, without requiring a config change and redeploy every time an instance moves. The tradeoff is the added infrastructure dependency of running and keeping the registry itself healthy and available.
What does the "Service Discovery Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to service discovery vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.