Map CRUD to HTTP correctly
Given a Todo resource, choose GET/POST/PUT/PATCH/DELETE routes and matching success status codes (200, 201, 204). Keep routes noun-based.
Remember REST
Full name: Representational State Transfer
Memory aid: Representations transfer State through constrained interactions.
A JSON endpoint is not automatically a fully RESTful design.
Study area: Data & integration · Batch 4
Relevant study for: Azure Data Fundamentals DP-900 · CompTIA Cloud+
Practice with exam flashcards →Legacy & Roots / Knowledge library
REST
architectural style for stateless web apis
Why learn REST?
REST provides a consistent way to expose and consume resources over the web so clients and servers can evolve independently, scale horizontally, and use standard HTTP features like caching and status codes.
Where it came from
REST was defined by Roy Fielding in his 2000 dissertation as an architectural style, not a protocol. It emerged from lessons learned while designing the early web architecture. Core constraints include client-server, statelessness, cacheability, uniform interface, layered system, and optional code-on-demand. REST became the dominant public API style in the 2010s and remains foundational, though now considered mature/legacy in many stacks.
- REST was defined by Roy Fielding in his 2000 dissertation as an architectural style, not a protocol.
- It emerged from lessons learned while designing the early web architecture.
- Core constraints include client-server, statelessness, cacheability, uniform interface, layered system, and optional code-on-demand.
- REST became the dominant public API style in the 2010s and remains foundational, though now considered mature/legacy in many stacks.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- Given a Todo resource, choose GET/POST/PUT/PATCH/DELETE routes and matching success status codes (200, 201, 204). Keep routes noun-based.
- Design GET /products with pagination, filtering, ETag, and 304 handling. Include sample request/response headers.
- Convert endpoints like /createUser and /getUserById into resource-oriented routes. Add proper status codes for validation, not found, and conflicts.
- Propose a v1 to v2 migration plan using additive changes, deprecation headers, and compatibility tests.
- Define a reusable error response schema (code, message, details, traceId) and map it to 400/401/403/404/409/422/500.
More ways to practice
Design a cache-friendly list endpoint
Design GET /products with pagination, filtering, ETag, and 304 handling. Include sample request/response headers.
Refactor RPC endpoints to REST
Convert endpoints like /createUser and /getUserById into resource-oriented routes. Add proper status codes for validation, not found, and conflicts.
Versioning without breakage
Propose a v1 to v2 migration plan using additive changes, deprecation headers, and compatibility tests.
Error model standardization
Define a reusable error response schema (code, message, details, traceId) and map it to 400/401/403/404/409/422/500.
Documentation and sources
- Fielding dissertation: REST architectural style (www.ics.uci.edu)
- RFC 9110: HTTP Semantics (www.rfc-editor.org)
- MDN: HTTP request methods (developer.mozilla.org)
Catalog research notes
- HTTP semantics were consolidated in RFC 9110 (2022), clarifying method and status code behavior used by REST APIs.
- HTTP/2 and HTTP/3 improved transport speed and multiplexing, while REST constraints remained unchanged.
- Modern REST practice now commonly includes OpenAPI contracts, linting, and contract testing for consistency.