What's the origin of REST architectural style?
- 1. Lightning talk What’s the origin of REST architectural style?
- 2. 1990-1991 WorldWideWeb project by Tim Berners-Lee: ● Uniform Resource Identifier (URI) ● HyperText Transfer Protocol (HTTP) ● HyperText Mark-up Language (HTML) ● First web server: http://info.cern.ch ● First web browser: Nexus ● First WYSIWYG HTML editor
- 3. August, 1991 The Web’s first page “The WorldWideWeb (W3) is a wide-area hypermedia information retrieval initiative aiming to give universal access to a large universe of documents.” Tim Berners-Lee
- 4. Web started to grow… exponentially…
- 5. 1993 Roy Fielding Co-founder of the Apache HTTP Server Project Web’s scalability
- 6. 1993 Roy Fielding Co-founder of the Apache HTTP Server Project Web’s scalability is governed by a set of key constraints Satisfy all of the constraints uniformly Six categories of constraints = Web’s architectural style
- 7. 1993 Roy Fielding Co-founder of the Apache HTTP Server Project Web’s architectural style 1)Client-server 2)Uniform interface 3)Layered system 4)Cache 5)Stateless 6)Code-on-demand
- 8. Web’s architectural style Client-server Separation of concerns
- 9. Web’s architectural style Uniform interface 1)Identification of resources URI 2)Manipulation of resources through representations 3)Self-descriptive messages 4)Hypermedia as the engine of application state (HATEOAS)
- 10. Web’s architectural style Uniform interface 1)Identification of resources 2)Manipulation of resources through representations Resource != representation Representation = a way to interact with the resource Representations: HTML, JSON, … 3)Self-descriptive messages 4)Hypermedia as the engine of application state (HATEOAS)
- 11. Web’s architectural style Uniform interface 1)Identification of resources 2)Manipulation of resources through representations 3)Self-descriptive messages resource’s desired state = client’s request resource’s current state = response from server They may include additional details (metadata) 4)Hypermedia as the engine of application state (HATEOAS)
- 12. Web’s architectural style Uniform interface 1)Identification of resources 2)Manipulation of resources through representations 3)Self-descriptive messages 4)Hypermedia as the engine of application state (HATEOAS) Resource’s state representation includes links to related resources (available “actions”)
- 13. Web’s architectural style Layered system Proxies, gateways, … Network-based intermediaries ● Intercept client-server communication for a specific purpose ● Used for enforcing: Security Response caching Load balancing
- 14. Web’s architectural style Cache ● To reduce client-perceived latency ● To increase the overall availability and reliability of an application ● To control a web server’s load It reduces the overall cost of the Web
- 15. Web’s architectural style Stateless ● A web server is not required to memorize the state of its client applications. ● Each client must include all of the contextual information that it considers relevant in each interaction with the web server. The web server can service a much larger number of clients.
- 16. Web’s architectural style Code-on-demand Examples: Java applets, Flash, JavaScript, … Optional constraint, why? Coupling between web servers and their clients (the client must be able to understand and execute the code that it downloads on-demand from the server)
- 17. Standards ● HTTP/1.1 ● RFC 3986 (syntax of URI)
- 18. After 2000 (Web’s scalability crisis) ● “Representational State Transfer” (REST) Ph.D. dissertation about Web’s architectural style by Roy Fielding