2. Design a Distributed Rate Limiter
Enforce tenant quotas across servers while making burst behavior and outage policy explicit.
Start with a template. Work through each step. Ask Coach when you need a second opinion.
Company tags are community-reported. Counts on cards show how many people reported that design.
Enforce tenant quotas across servers while making burst behavior and outage policy explicit.
Deliver email, push and SMS with preferences, retries and honest delivery status.
Route API traffic with authentication, tenant limits and safe configuration rollout.
Safely converge 40,000 gateways while some sites are disconnected and old controllers can return.
Survive a regional outage without confusing a health check with safe recovery.
Any request can time out after the server has already acted. The client cannot tell that from a request that never arrived, and the only safe response to uncertainty is to retry — which, without help, charges the card twice.
Signed HTTPS callbacks for a billion events a day, at least once, retried for three days, with no endpoint able to slow another.
Detect, classify and repair failing GPU nodes (Xid errors, ECC, NVLink and EFA faults, stragglers, silent corruption) without draining the fleet.