Quick Answer
How to explain a rate limiter in English: clarify identity and limits, pick an algorithm, place it before expensive work, then name fairness and failure tradeoffs.
Diagrams and what to say while drawing
Narrate each figure out loud. Point to the box you are talking about.
What to say on figure 1
Client → rate limiter → API servers.
What to say on figure 2
Show the token bucket filling and consuming tokens.
What to say on figure 3
Show a 429 response path when empty.
What to say on figure 4
Show a shared Redis-style counter for multi-server limits.
Key vocabulary
| Term | Plain meaning | Say it in an interview |
|---|---|---|
| Rate limit | Max requests in a time window | “I’d rate-limit by API key.” |
| Token bucket | Tokens refill over time | “A token bucket allows short bursts.” |
| Throttle | Slow or reject excess traffic | “Excess requests are throttled with 429.” |
| Quota | Allowed usage budget | “Each client gets a daily quota.” |
ESL English phrases and transitions
Clarify
- “Are we limiting by user, IP, or API key?”
- “Is the goal to protect the system, enforce fairness, or both?”
Propose and check in
- “The next bottleneck is X, so I would add Y.”
- “Does this level of detail work, or should I go deeper?”
Tradeoffs
- “The advantage is simplicity; the downside is…”
- “I’d choose A over B because…”
Key English language pitfalls
| Pitfall | Sounds like | Say instead |
|---|---|---|
| Algorithm dump | Listing every algorithm | Pick one, say why, name one tradeoff |
| Ignoring bursts | Fixed window only | “Token bucket allows controlled bursts.” |
| Summary | Every new box needs one spoken reason. | |
Common English mistakes
| Mistake | What the interviewer concludes | Better English |
|---|---|---|
| No identity key | Unclear who is limited | “Limit by user ID or API key.” |
| No rejection English | Vague failure | “We return HTTP 429 Too Many Requests.” |
What the interviewer is testing
This is a communication test as much as a design test. Can you explain rate limiting as a calm collaboration?
Interviewers listen for structure, tradeoffs, and clear English under pressure.
Key takeaway
Your job is to narrate decisions the interviewer can follow and challenge — not to dump tools.
How to open the problem in English
Opening script you can practise aloud
- “Are we limiting by user, IP, or API key?”
- “Is the goal to protect the system, enforce fairness, or both?”
Watch Out
Do not open with a finished architecture. Show the path.
Rate limiter system design
Use this sequence for rate limiter system design. For each stage, say what changes, why, and what can still go wrong.
Rules
Define identity, window, and limit — soft vs hard block.
Algorithm
Compare token bucket vs fixed window in one clear sentence each.
Placement
Put the limiter at the gateway/edge before expensive work.
Distributed
Use a shared store for counters across servers; mention race conditions briefly.
Weak vs strong answers
Weak
“Just use Redis.”
Strong
“I’d limit by API key with a token bucket at the gateway, return 429 with a retry-after, and store counters centrally so all nodes agree.”
Metrics and how to say numbers
| Write | Say |
|---|---|
| 100 req/min | one hundred requests per minute |
| HTTP 429 | four twenty-nine / too many requests |
Follow-up questions you will get
Likely follow-ups
- “How do you sync limits across regions?” → “I’d start with a regional limiter and discuss global quotas if needed.”
Practice drill
Checklist
- Clarify identity
- Pick algorithm
- Draw placement
- Explain 429
“If you can explain rate limiting without notes, you are ready to draw it in an interview.”
Answer frameworks you can reuse
Use these spoken templates under pressure. Fill the blanks — do not invent a new structure mid-interview.
Framework 1 — Whole answer
Clarify → High-level → Deep dive → Check-in.
Framework 2 — Each component (B-C-B-C)
Bottleneck → Component → Benefit → Cost.
Framework 3 — Now → Breaks → Next
Current design → failure mode → next upgrade.
Framework 4 — Draw → Name → Why → Risk
Narrate every box as you draw it.
Interview tip
Pick one framework and stay inside it. Switching structures mid-talk makes English sound messy.
Frequently Asked Questions
Tap a question to expand the answer.