Service Discovery

This lesson covers Service Discovery. If this feels new, that is normal. We will build up slowly.

What you will learn

• What service discovery means — in normal words, not textbook words
• How it works step by step
• Code you can run today on your laptop
• Where teams use this in real projects

Before you start

• Software: Node.js LTS from nodejs.org, VS Code, and a terminal
• Knowledge: Earlier lessons in this Node.js course
• Previous lesson: API Gateway — Complete Guide

Explain it simply

Service discovery helps services find each other's addresses in the cloud where IPs change often.

Why developers use this

• For larger teams and scale
• Learn concepts before you need them
• Helps system design talks

How it works (step by step)

1. Identify the real problem (scale, team size, CPU load).
2. Apply Service Discovery to that problem only.
3. Keep observability: logs, metrics, health checks.
4. Load-test before and after so you know it helped.

Code example — type this yourself

// Kubernetes gives stable DNS: http://users-service.default.svc.cluster.local

On Kubernetes, Services provide DNS names. Locally, use docker-compose service names.

What each part does

• // Kubernetes gives stable DNS: http://users-service.default.svc.cluster.local — Line 1: runs as written.

Real life: where Service Discovery shows up

A growing SaaS product introduces Service Discovery only after the monolith gets painful — measured traffic, not guesswork, drives the change. In interviews, explain the trade-off you chose and what you would measure in production.

Try it yourself — hands-on

1. Create a new file (e.g. service-discovery-demo.js) in an empty folder
2. Type the example code for Service Discovery yourself — typing helps memory
3. Run node on that file and read the output
4. Change one line (a value, a message, a route path) and run again to see what breaks or improves

Common mistakes (avoid these)

• Skipping the terminal — Service Discovery only feels easy after you run code yourself.

Interview note

Senior interviews may ask how Service Discovery behaves under load, failure, or security review — mention logging, timeouts, and validation.

Summary

• You can explain Service Discovery in your own words
• You ran working code — not just read about it
• You know one mistake to avoid and one real place teams use this