Health Check & Service Discovery · View 09 of 21 · Structure
The two contracts
- Inbound: every input is attributed to a registered identity, and an instance may report only about itself.
- Outbound: every view carries its version and its staleness, and no surface may be read synchronously on a request.
- The resolution API is for tooling and target-group sync. A caller using it on the hot path has misunderstood the design.
Deliberate omissions
- Edge labels were cut to the single constraint that matters on each side; each interface's `sub` names what it carries.
- Health reporting rides the Instance API rather than getting a surface of its own — one identity, one lease, one contract.
Assumptions
- 150,000 resolution API calls/second, of which ≥ 99% are expected to be served from client cache and never arrive.