CSE Roadmap

Core tier · about 3 hours · 8 parts

Part 1 of 8 · 1 min read

Why this page comes first after CDNs

In this module you will

  • Say what state is, and tell a stateful server from a stateless one.
  • Follow a login through a cookie and a session store, and size that store with simple arithmetic.
  • Compare a server-side session with a signed token, including how each is revoked.
  • Explain what sticky sessions cost, and when they are still the right choice.
  • Move each kind of state out of a web server, and name the new home for it.
  • Name the parts of a design that stay stateful on purpose, and how to route to them.

Load balancers and autoscaling work well only when any server can answer any request. That is true only when servers keep nothing important in their own memory. This page shows where that "something important" goes instead. Every case study from Level 10 uses the answer. The numbers on this page are made up to show the idea, unless the text names a book.