Скачать или смотреть Service Discovery for Microservices: DNS, Registry, and Mesh Basics

Service discovery keeps microservices reachable as pods scale, restart, and move. This video explains the end‑to‑end loop: providers register with a service registry, consumers fetch healthy instances with metadata, and requests route either directly (client‑side discovery) or through a load balancer or mesh (server‑side discovery). Learn the trade‑offs, resilience patterns—retries with backoff, circuit breakers, outlier detection, zone‑aware routing—and how health checks, TTLs, and version metadata enable canaries and blue‑green rollouts.

What you’ll learn:

What a service registry does and why it’s essential for dynamic environments

Client‑side vs server‑side discovery: latency, control, and complexity trade‑offs

Health checks, TTL/leases, metadata, and push updates for fast convergence

Reliability patterns: retries, timeouts, circuit breakers, outlier ejection

How meshes and Kubernetes DNS fit in, plus when to choose each approach

Chapters:
0:00 Intro
0:22 What is a service registry
0:58 Client‑side discovery
1:34 Server‑side discovery
2:06 Health, TTLs, and metadata
2:32 Resilience and rollouts
2:56 Which approach to use

CTA
If this helped, like and subscribe to Bazai. Comment with the current stack: DNS only, registry + SDK, or service mesh.