How do I build smart rate limiting against distributed brute force and DDoS?
Per-IP limits lose to rotating proxies, so key the Redis sliding-window on account + IP + ASN, add account lockout and leave volumetric floods to the edge.
Tag
Reliability and resilience: service levels, error budgets, on-call, timeouts, retries, backoff and bulkheads, so a system works as reliably as promised. questions under this tag, answered directly. (Page 2/2)
15 answered questions carry this tag.
Per-IP limits lose to rotating proxies, so key the Redis sliding-window on account + IP + ASN, add account lockout and leave volumetric floods to the edge.
Split the critical path (browse, cart, checkout) from the nice-to-haves, put those behind feature flags with short timeouts, and rehearse the kill-switch.
Split the transaction into local steps with compensating actions, driven by one orchestrator over a queue, each idempotent and published through an outbox.
Don't hand-roll failover: put promotion behind a Patroni + etcd quorum, and let a primary cut off from the majority demote itself by fencing.
A breaker alone won't hold: pull connect_timeout and timeout down to 800ms-2s, isolate the dependency behind a bulkhead, and define a cached fallback.