What is service discovery and why do you need it behind a load balancer?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
Instances come and go with autoscaling, so callers cannot hardcode IPs.
WHY — Microservices instead of guessing?
Why interviewers care about Microservices:
who only read docs from people who shipped.
and tied to Backend work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Instances come and go
with autoscaling, so callers cannot hardcode IPs.
- 2A registry such as
Eureka, Consul, or Kubernetes DNS maps a logical name to healthy pods.
- 3The load balancer or
client-side balancer then picks an instance.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Instances come and go with autoscaling, so callers cannot hardcode IPs. A registry such as Eureka, Consul, or Kubernetes DNS maps a logical name to healthy pods.