This topic is a project lesson inside the APIs & Communication Styles module. The goal is not to memorize the title: reconstruct the problem it solves, the mechanism that makes it work, and the signal that tells you when to use it.
Remember the shape, not the sentence
“REST for resources, gRPC for speed, WebSockets for realtime.”
What problem does this solve?
Start from the engineering problem rather than the definition. Design the API contract for a tiny URL shortener exists because a system needs a reliable way to handle a recurring constraint inside APIs & Communication Styles. Ask what would become slow, ambiguous, unsafe, or impossible without it.
How the mechanism works
Break the idea into observable steps. The useful mental model is: input → transformation → decision or state change → output. Keep each step small enough that you can redraw it from memory. The surrounding module is the context: REST for resources, gRPC for speed, WebSockets for realtime.
When to reach for it
Use nearby concepts as contrasts. In this module, compare Design the API contract for a tiny URL shortener with REST design: resources, verbs, idempotency, GraphQL & gRPC: when each beats REST, Long polling vs Server-Sent Events vs WebSockets. The distinction matters because good engineering choices depend on the constraints, not on memorizing isolated definitions.
See the mechanism before you memorize it
One diagram, one causal story, one reconstruction task.
Design the API contract for a tiny URL shortener — causal map
Frame
State the problem and the constraints before naming the technique.
Transform
Apply the core mechanism of Design the API contract for a tiny URL shortener and track what state changes.
Observe
Inspect the artifact, output, invariant, or behavior produced by the mechanism.
Transfer
Explain where the same idea appears elsewhere in System Design Fundamentals.
Draw the idea yourself
Rebuild the core flow on a real canvas before moving to the worked walkthrough.
Walk the system
Frame
State the problem and the constraints before naming the technique.
Transform
Apply the core mechanism of Design the API contract for a tiny URL shortener and track what state changes.
Observe
Inspect the artifact, output, invariant, or behavior produced by the mechanism.
Transfer
Explain where the same idea appears elsewhere in System Design Fundamentals.
Reconstruction card
Use the card as a generative note, not a summary to copy. Fill it from memory after the explanation.
TOPIC: Design the API contract for a tiny URL shortener
MODULE: APIs & Communication Styles
TYPE: project lesson
PROMPT
What problem does it solve?
What changes step by step?
What evidence proves it worked?
When would you choose something else?What usually goes wrong
Close the tab. Rebuild it from memory.
Read the question, answer aloud, then reveal.
What problem is Design the API contract for a tiny URL shortener designed to solve?Reveal answer
It addresses a recurring constraint inside APIs & Communication Styles. A strong answer names the input, the core mechanism, and the result rather than repeating the title.
What are the four stages of the mental model?Reveal answer
Frame the problem → transform the input/state → observe the evidence → transfer the idea to a new scenario.
Why is gRPC faster than REST/JSON?Reveal answer
Binary Protocol Buffers over HTTP/2: smaller payloads, multiplexed streams, and generated typed clients — at the cost of human-readability and browser support.
What makes an operation idempotent and why does it matter?Reveal answer
Repeating it has the same effect as doing it once — retries after timeouts are then safe (PUT/DELETE are idempotent; POST is not).
Make this idea travel.
Connect it next to: Vertical vs horizontal scaling • Latency, throughput, bandwidth — with real numbers • Interactive: numbers every engineer should know • Availability, nines, and single points of failure.