Gateway RidgeISSUE #16 of 35

discovery · service registry · dns

Gateway GusVSTimeout Titan

Gateway Gus saysService discovery lets services find each other dynamically instead of hardcoding addresses.

In dynamic environments, service instances come and go with changing IPs. A service registry tracks healthy instances; clients query it (or DNS-based discovery) to find a current address. This decouples callers from fixed locations and enables elastic scaling. Kubernetes does it via internal DNS and services; standalone systems use Consul/etcd.

Power-ups you unlock

Find services dynamically, not by hardcoded IP
A registry tracks healthy instances
DNS-based discovery is common (K8s)
Enables elastic scaling and resilience

Timeout Titan attacks — common mistakes

Hardcoding service IPs/ports
No health filtering (routing to dead instances)
Stale registry entries

Boss battleExplain why hardcoding a service’s IP breaks in an autoscaling cluster.

Example code

<!doctype html><html><head><meta charset="utf-8"></head>
<body style="background:#06040d;color:#e6e0ff;font-family:monospace;padding:20px"><pre>hardcoded: call 10.0.1.7  → instance dies → broken
discovery: call "orders-svc" → registry → a healthy IP</pre></body></html>

▶ Open the interactive comic issue

‹ Service Mesh · Sidecar Proxies Health Checks · Liveness · Readiness ›