Everything that goes into building a correct, fast, safe backend service: HTTP and REST, auth, SQL, indexing, transactions, and the caching/queueing patterns that keep it standing up. Language- and vendor-agnostic.
You’re reading a free preview. Sign up to see every topic and question — and to play this deck as games.
The contract every backend service speaks: methods and their guarantees, the status codes that actually mean something, conditional requests, and how to shape a resource API.
73 total questions
Card #1
What do the HTTP status classes 2xx and 3xx mean?
Card #2
When should an API return 401 rather than 403?
Card #3
What does it mean for an HTTP method to be idempotent, and which methods are?
1. A client sends a well-formed request but its access token has expired. Which status code is most appropriate?
2. Which group of HTTP methods is entirely idempotent?
3. An API creates a new order in response to POST /orders. The most appropriate response is:
1. A successful POST that creates a resource should return status ___ together with a Location header.
Hint: Three digits
2. Status code ___ means the caller is authenticated but not permitted to perform the action.
Hint: Not the one about missing credentials
3. An HTTP method is ___ when repeating the identical request leaves server state the same as sending it once.
Hint: PUT and DELETE have this property
