The encyclopedia · Engineering & Operations · Technical decision · 2000-2020s
Fielding didn't invent a protocol, he described the web — and that became REST
Roy Fielding's 2000 dissertation named the principles already making the web work, and that lightweight description beat SOAP to become the API standard.
University of California, Irvine
the move
In the 1980s and 1990s, distributed computing models such as RPC and CORBA let systems talk to each other, but they were complex, rigid and built for closed environments. The web, by contrast, had taken off because it was simple: a browser asks for a page, a server answers, and hyperlinks connect it all.
In 2000 Roy Fielding, in his doctoral dissertation at UC Irvine, gave that success a precise name. REST, Representational State Transfer, is an architectural style drawn from the constraints that had already made the web work — separating client from server, keeping requests stateless, addressing resources by URL, and using the standard HTTP methods to act on them.
Crucially, Fielding did not invent a new protocol or require anyone to install anything. REST was a way of thinking, which is why it was cheap to adopt. Against SOAP's strict messaging envelopes and elaborate service definitions, REST's familiar HTTP methods and web addresses made development faster and integration easier.
With JSON replacing XML as the lightweight payload, and big internet companies opening public APIs, REST became the dominant design for the programmable web, powering mobile apps and the cloud services that built on top of it.
why it works
- Distributed systems like RPC and CORBA were rigid and hard to scale
- Fielding named real constraints instead of shipping a product
- Stateless, resource-based design matched the web developers already knew
- It avoided SOAP's heavy messaging envelope and service definitions
- JSON made the payload light, so the whole stack stayed simple
what transfers
Sometimes the strongest design move is not to invent a new mechanism but to name and reuse the constraints that already work, because then adoption costs nothing extra.
what came after
REST became one of the dominant ways software systems communicate across the internet, central to public APIs, mobile apps and early microservices. Even newer approaches like GraphQL and gRPC sit alongside rather than replace it, because REST's familiarity and tie to the structure of the web remain an enormous advantage. The hypermedia constraint Fielding insisted on, however, is still widely ignored.
references
- REST API (Engineering and Technology History Wiki)
- What is REST? The de facto web architecture standard
spotted an error? The archive wants to know.