CSE Roadmap

Core tier · about 4 hours · 8 parts

Part 1 of 8 · 1 min read

Why this page comes first in Level 10

In this module you will

  • Ask the questions that fix the scope of a rate limiter, and write the needs as numbered requirements.
  • Estimate request rate, counter memory and store load with simple arithmetic.
  • Place the limiter (client, server, gateway) and justify the choice.
  • Explain the two problems of many servers, races and synchronisation, and fix them.
  • Describe what a refused client sees, and what to monitor afterwards.

Level 1 explained the five counting methods. This page puts them inside a whole system. A rate limiter is a good first case study because it is small, it touches a shared store, and it forces the question "what if two servers count at once?". The book used is "System Design Interview" by Alex Xu, chapter 4. The numbers marked "made up" only show the idea. The code at the end of module 2 in Level 7 of the low-level track builds the same algorithms inside one process. This page is about the system around them.