Foundationv1Reliability
Rate limits and backpressure
Shape traffic by contract and scope instead of sending oversized batches or synchronized retry storms.
Limit scope
A limit may apply to a credential, business, branch, endpoint, or a combination. Never assume one global number unless an endpoint reference publishes it.
Client behavior
- Honor Retry-After when returned.
- Use a queue and local concurrency cap.
- Batch only when the contract defines batch semantics and size.
- Open a temporary circuit after repeated dependency failure.
Server behavior
Use 429 for an expected limit and never disguise overload as empty success. Record safe metrics without sensitive payloads and return a correlation_id.