The encyclopedia · Software & IT · Technical decision · 2000–2010
REST standardized the web's interface and became the default API architecture
Fielding's dissertation turned the web's own constraints into a style, and every API followed
University of California, Irvine
the move
Roy Fielding defined Representational State Transfer in Chapter 5 of his 2000 doctoral dissertation at UC Irvine, describing the architectural style behind the web: client-server separation, stateless requests, caching, a layered system, and a uniform interface.
The central move was the uniform interface: resources identified by URL, manipulated through representations, with self-descriptive messages. Instead of inventing an RPC call per service, the web reused the same small set of HTTP verbs across every resource.
That constraint set — written by the same person who co-authored HTTP/1.1 — spread from the web itself to API design. REST became the default way to expose services, and the browser's generic clients worked against any conformant server without bespoke code.
why it works
- One uniform interface means any HTTP client can interact with any REST service
- Statelessness lets any server handle any request, making horizontal scaling trivial
- Resource-based design decouples clients from implementation details and lets both evolve
- Self-descriptive messages let intermediaries cache, transform, and route without per-service logic
what transfers
The constraint that wins is the one applied to the shared interface: when every client speaks the same verbs to every server, ecosystems scale without anyone coordinating implementations.
what came after
REST became the dominant architecture for public web APIs, shaping every major platform's developer story and the tooling around HTTP services. Its principles were later encoded in API specifications like OpenAPI, and its stateless-resource model still underlies the API economy.
references
- Architectural Styles and the Design of Network-based Software Architectures, Chapter 5: Representational State Transfer (REST)
- RFC 2616: Hypertext Transfer Protocol — HTTP/1.1
spotted an error? The archive wants to know.