API gateway for system design interviews
API gateway for system design interviews. The jobs the hop is good at, what must stay behind it, and a chat or feed that needs one.
Moving requests through a system without losing or repeating work: load balancing, rate limiting, queues and idempotency.
API gateway for system design interviews. The jobs the hop is good at, what must stay behind it, and a chat or feed that needs one.
Backpressure in system design interviews. Slow consumers, bounded queues, drop versus block, and how you apply it across a network hop.
Circuit breaker pattern for interviews. Closed, open, and half-open, what trips the breaker, honest fallback, and where it lives next to retries.
Reverse proxy for system design interviews. TLS, buffering, caching, and the mistakes that turn the hop into a bottleneck.
Idempotency keys in system design. How a client retries a payment or a create without doubling the effect, and where the key has to be stored.
Load balancing for system design interviews. Round robin, least connections, and consistent hashing, and when layer 4 and layer 7 change the answer.
Message queues for system design interviews. What a queue is for, how it differs from a log, and which delivery guarantee you should claim.
Rate limiting for system design interviews. Token bucket, leaky bucket, and fixed windows, plus how a limit stays correct across more than one server.