REST (Fielding dissertation)
- Category
- Data and API specs
- Docs outline
- 8 sections
Official docs outline
ics.uci.edu- Deriving REST
How REST is derived from architectural constraints.
- Client-server
Separation of concerns between UI and data storage.
- Stateless
Each request contains all necessary context.
- Cache
Cacheable responses to reduce interaction.
- Uniform interface
Resource identification, manipulation through representations, self-descriptive messages, hypermedia.
- Layered system
Intermediaries such as proxies and gateways.
- Code on demand
Optional downloading of executable code.
- REST architectural elements
Data elements: resources, identifiers, representations, and metadata.
Each section links to the official page. Titles and summaries by Extra Credit; the docs belong to their authors.