CSE Roadmap

Core tier · about 3 hours · 9 parts

Part 1 of 9 · 1 min read

Why this page comes first after the path of a request

In this module you will

  • Say what an API is, and choose between REST, gRPC and GraphQL for a given caller.
  • Design a small REST API: resource names, methods, status codes and an error body.
  • Explain safe and idempotent methods, and make a payment-style request safe to retry with an idempotency key.
  • Page through a large list with an offset and with a cursor, and say why the cursor wins on big tables.
  • Change an API without breaking old callers, using versions and compatible changes.

The previous page followed one request across the network. This page looks at what the request says. Every box in a later design has an API at its edge. An interviewer often asks for the two or three calls of a system before any drawing, so the habit of naming them well pays off in every case study.

Numbers on this page are made up to show the idea, unless the text names a book.