Finding services
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
explain why hard-coded addresses fail and the two discovery styles.
Planned topics
- Instances come and go (scaling, deploys, crashes); their IPs change.
- Client-side discovery: the client asks a registry for instances and picks one itself.
- Server-side discovery: the client calls a stable name or load balancer, which picks an instance.
- Both need to know which instances are healthy.
- Prefer what the platform already provides; add a registry only if you need one.
Draft outline details
Demonstration
| Style | Who picks the instance | Example |
|---|---|---|
| Client-side | the caller | Eureka, Consul + client library |
| Server-side | a proxy or platform | Compose DNS, Kubernetes Service |
Check your understanding
Why is http://10.0.0.17:8080 a poor service address?
Show answer
The instance may move, die, or be replaced.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.