TOUGH TONGUE AI
  • Home
    LogoTOUGH TONGUE AI

    RESOURCES

    Loading...

    HomeLibrarySD Coach · Rate Limiting

    SD Coach · Rate Limiting

    SD Coach · Rate Limiting

    Overview

    How does an API say "slow down" fairly, in a millisecond, across dozens of servers? In Nora's 3D lab you tap to predict how a fixed window leaks double its limit, how many requests a token bucket lets through, and what happens when two gateways read the same counter at once. Then you fix each one and decide what the limiter does when it breaks.

    Your Instructions

    Your goal: design a distributed rate limiter and defend the algorithm you pick.

    How this works (about 25 minutes)

    • Nora's 3D lab sits beside the call. When it asks you to predict, tap your guess or say it, then watch it change.
    • The counter-store estimate goes on the notepad. Say your working aloud.
    • One multiple-choice check.

    Tips

    • HTTP 429 means "Too Many Requests".
    • Read the module reading first: Rate Limiting.
    • Interrupt any time with a question.

    More in System Design Interview Prep: AI Coach Edition

    • SD Mock · Design Pastebin
    • SD Coach · News Feeds and Typeahead
    • SD Mock · Design Facebook News Feed
    • SD Mock · Design Twitter
    • SD Mock · Design Typeahead Suggestion
    • SD Mock · Design Twitter Search
    • SD Mock · Design an API Rate Limiter
    • SD Coach · Event-Driven Systems and Notifications
    • SD Mock · Design a Notification System
    • SD Coach · Async Jobs, Schedulers and Crawlers
    • SD Mock · Design a Web Crawler
    • SD Coach · Distributed Storage
    View the full course (43 sessions) →