2000
REST architectural style defined
Roy Fielding's 2000 doctoral dissertation defined Representational State Transfer (RESTRepresentational State Transfer — a style for web APIs using HTTP methods and resource URLs.) — an architectural style for scalable network APIs using HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages. resources and hypermedia.
What it was for
RESTRepresentational State Transfer — a style for web APIs using HTTP methods and resource URLs. is not a library — it is a design approach: expose resources as URLs, use HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages. verbs (GET, POST, PUT, DELETE), keep servers stateless, and cache responses. Most 'RESTRepresentational State Transfer — a style for web APIs using HTTP methods and resource URLs. APIs' today are HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages.+JSONJavaScript Object Notation — a lightweight text format for structured data exchange on the web. without hypermedia, but the dissertation still names the constraints teams aim for. Fielding co-authored HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages./1.1 while writing it.
People
- Roy Fielding — author
Why it's here
RESTRepresentational State Transfer — a style for web APIs using HTTP methods and resource URLs. gave a vocabulary for why the web's architecture scales — and influenced every public HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages. APIApplication programming interface — a defined way for programs to talk to each other or to a service. since.
Why it mattered
It separated resource design from RPC-style endpoints and became the default mental model for web services.
What it solved
Ad-hoc HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages. APIs lacked shared constraints; developers needed principles for cacheable, layered, scalable systems.
Media
ImageRoy FieldingPhil Whitehouse, CC BY 2.0, via Wikimedia Commons
Related
- GraphQL technical preview open-sourcedJuly 1, 2015
- gRPC open-sourcedFebruary 26, 2015
- HTTP/2 standardizedMay 14, 2015
- SOAP 1.1 publishedMay 8, 2000
- Swagger 1.0 releasedAugust 10, 2011
- JSON-RPC 1.0 published2005