Rate Limiting Without the Hype

Abstract code gradient artwork

Small pull requests get real reviews, large ones get approvals. If the error message does not say what to do next, it is half an error message. Our on-call rotation improved the day we deleted half of the alerts.

What didn’t

Most production incidents start as a small assumption nobody wrote down. Latency percentiles tell a story that averages politely hide. Tests are documentation that fails loudly when it goes stale.

Naming things well saved us more time than any framework migration. The best architecture diagram is the one the new hire can redraw from memory.

Getting started

Logs answer questions you knew to ask; traces answer the ones you did not. Small pull requests get real reviews, large ones get approvals. Security is mostly about saying no to defaults that were convenient in 2010. Tests are documentation that fails loudly when it goes stale.

The best architecture diagram is the one the new hire can redraw from memory. A boring deploy pipeline is a feature, not a lack of ambition.

The short version

We wrote the migration twice: once to learn, once to ship. The rollback plan should exist before the rollout plan is approved. Security is mostly about saying no to defaults that were convenient in 2010.

Latency percentiles tell a story that averages politely hide.

The fastest query is the one you never send, but the second fastest has a good index. We wrote the migration twice: once to learn, once to ship.

Code

Takeaway

The rollback plan should exist before the rollout plan is approved.

Most production incidents start as a small assumption nobody wrote down. Latency percentiles tell a story that averages politely hide.

Comments

2 responses to “Rate Limiting Without the Hype”

  1. Amara Avatar
    Amara

    Clear and calm, like always. Nice one.

  2. Great write-up. The part about the trade-offs was spot on.

Leave a Reply

Your email address will not be published. Required fields are marked *