Technical detail · Service API Contracts: Versioning and Compatibility
DNS, health and regional failover
DNS maps names to network addresses. Its time to live, or TTL, sets how long an answer may be kept in a cache before a fresh lookup.
DNS and global routing are useful for public entry points and regional routing. Failover switches traffic to a backup when a destination fails. Pair it with health checks, automatic tests that show whether a service is working, and operational runbooks, written steps for handling problems. Review the path in order: a stable name selects a region or gateway, health policy removes an unsafe destination, and the client observes TTL and retry rules before another lookup. The contract must also say what happens to active sessions and writes during failover. This keeps global discovery aligned with the chapter’s promise that clients depend on stable behavior rather than current instance addresses.