catalog / infra

Load Balancer

Spread traffic across healthy backends without dropping requests.

16 capabilities 1 sections reference specification

Build against it

# give your agent the catalog — no account, no install
claude mcp add provespec -- npx -y provespec-mcp

# then, from any agent session
spec_get(slug: "load-balancer")                → the capability tree
spec_checklist(slug: "load-balancer")          → the questions to answer
spec_grade(slug: "load-balancer", grades: [...])  → parity % + the gap list

# or just fetch it
curl https://provespec.com/catalog/load-balancer/spec.json

Grade every capability below as yes · partial · no · na, with a file reference as evidence. Whatever you leave ungraded counts as missing — the gap list is the work queue.

Or just paste this to your agent

Use the ProveSpec MCP server. Fetch the "load-balancer" spec with
spec_get, then walk spec_checklist and grade this repository against it —
one verdict per capability, each with a file reference as the note.
Call spec_grade with the results and give me the gap list as the plan.

If the server is not registered, add it first:
  claude mcp add provespec -- npx -y provespec-mcp

The specification

AI 16

Distribution
  • ✓ Algorithms round-robin, least-connections, hash
  • ✓ Weighted backends for heterogeneous capacity
  • ✓ Session affinity when required cookie or IP hash
Health
  • ✓ Active health checks with thresholds consecutive failures before ejection
  • ✓ Passive ejection on observed errors outlier detection
  • ✓ Automatic reinstatement when a backend recovers
Resilience
  • ✓ Retries with a budget, not unbounded retry storms are the failure mode
  • ✓ Circuit breaking per backend
  • ✓ Request and idle timeouts at every hop
Traffic
  • ✓ Connection draining on removal in-flight requests finish
  • ✓ Rate limiting and concurrency caps
  • ✓ Weighted routing for canary and blue-green
TLS
  • ✓ Termination, passthrough and re-encryption
  • ✓ Certificate rotation without dropping connections
Headers
  • ✓ Preserve or set forwarded-for and forwarded-proto
Observability
  • ✓ Per-backend latency, error rate and saturation
Open in Parity → Download spec.json All 102 specs