CSE Roadmap

Core tier · about 4 hours · 8 parts

Part 1 of 8 · 1 min read

Why this page comes first

In this module you will

  • Explain what a message queue is and name what it separates in time, in speed and in failure.
  • Show with small numbers how a queue absorbs a traffic spike, and how long a backlog takes to drain.
  • Tell load balancing from fan-out, and say what an acknowledgment and a visibility timeout do.
  • Explain why a failing message can loop forever, and how a retry limit and a dead letter queue stop it.
  • Decide when a queue helps and when a plain request and response is better.

Every later page in this level moves data through something that sits between two programs. This page introduces the simplest version, the queue, and the vocabulary that the rest of the level builds on. The books used are "Understanding Distributed Systems", "Designing Data-Intensive Applications", "System Design Interview" (volume 1) and "Building Microservices". The numbers are made up to show the idea, unless the text names a book.