01 / DECISION
When this primitive earns a place
Use load balancing when multiple origins can actually serve equivalent requests and health can be tested independently.
02 / ARCHITECTURE
Build the smallest defensible path
Define pools and monitor endpoints, select steering and failover semantics, then document stateful-session and data-consistency assumptions.
- 01Name the contract
Use load balancing when multiple origins can actually serve equivalent requests and health can be tested independently.
- 02Add one primitive
Define pools and monitor endpoints, select steering and failover semantics, then document stateful-session and data-consistency assumptions.
- 03Capture failure evidence
Take one pool out of service in a controlled test, measure detection and recovery time, and confirm sessions behave as designed.
03 / REPRODUCE
Evidence before confidence
Take one pool out of service in a controlled test, measure detection and recovery time, and confirm sessions behave as designed.
curl -fsS https://example.com/health04 / BOUNDARY
The production boundary
A shallow health check can route users to a broken dependency; a deep check can overload the service or create correlated failure.
05 / FIRST-PARTY SOURCES
Keep first-party sources authoritative
Product behavior, limits, pricing, and availability can change. Re-check these sources before acting.