Rest and the hypermedia constraint
Oct. 8, 2011•0 likes•7,737 views
Download to read offline
Report
Technology
News & Politics
A RESTful API is only truly RESTful if it uses hypermedia to tell us about all the actions that can be performed on the curent resource, allowing us to traverse the API from a single entry point. His session looks at REST and HATEOAS (Hypermedia As The Engine Of Application State) to illustrate good service structure. Ben will use the RESTful file sharing service fdrop.it to illustrate the various examples of how this can be used. This session is recommended for architects and senior developers alike and will give a good grounding in writing excellent, self-explanatory RESTful services.
InviqaFollow
Recommended
Model Your Application Domain, Not Your JSON StructuresMarkus Lanthaler
REST & RESTful Web ServicesHalil Burak Cetinkaya
Understanding REST APIs in 5 Simple StepsTessa Mero
Rest api standards and best practicesAnkita Mahajan
introduction about REST APIAmilaSilva13
Building Next-Generation Web APIs with JSON-LD and HydraMarkus Lanthaler
More Related Content
What's hot
Kong API Gateway Chris Mague
Introduction to the Web APIBrad Genereaux
RESTful API - Best PracticesTricode (part of Dept)
REST APITofazzal Ahmed
Design Beautiful REST + JSON APIsStormpath
REST-API introduction for developersPatrick Savalle
Viewers also liked
The Internet as Web Services: introduction to ReSTBruno Kessler Foundation
RESTful servicesgouthamrv
Introduction To RESTBhavya Siddappa
Learn REST in 18 SlidesSuraj Gupta
HATEOAS 101 - Opinionated Introduction to a REST API StyleApigee | Google Cloud
REST PresentationAlexandros Marinos
Similar to Rest and the hypermedia constraint
REST and the Hypermedia ConstraintInviqa
internet principles of operation By ZAKTabsheer Hasan
HTTP: the Other ESBRyan Riley
HTTP1.1/2 overviewAndrew Muntian
RESTful APIsAdi Challa
WebMayank Vora
Recently uploaded
The Flutter Job Market At The MomentAhmed Abu Eldahab
Machine learning with quantum computersSpeck&Tech
Easy Salesforce CI/CD with Open Source Only - Dreamforce 23NicolasVuillamy1
Unleashing Innovation: IoT Project with MicroPythonVubon Roy
Supplier Sourcing_Cathy.pptxCatarinaTorrenuevaMa
Improving Employee Experiences on Cisco RoomOS Devices, Webex, and Microsoft ...ThousandEyes
Rest and the hypermedia constraint
- 1. REST and HATEOAS Ben Longden, PHPNW 2011
- 2. REST and the Hypermedia Constraint Ben Longden, PHPNW 2011
- 3. Who are you?
- 4. Who are you? @blongden
- 5. Who are you?
- 6. Who are you? @ibuildings
- 7. Who are you?
- 8. Who are you? @fdrop
- 11. REST Series of constraints for distributed hypermedia systems - Roy Fielding, 2000
- 13. Constraints are good They (help) stop you from doing crazy things
- 15. REST is an Architecture It is not a protocol
- 16. Goals Scalability Generality of Interfaces Independent deployment of components Intermediaries to reduce latency, enforce security, and encapsulate legacy systems.
- 17. Client server
- 18. Stateless
- 19. Cache
- 20. Layered system
- 21. Code on demand
- 23. Uniform interface Identification of resources
- 24. Uniform interface Manipulations of resources through representations
- 25. Uniform interface Self descriptive messages
- 26. Uniform interface Hypertext as the engine of application state
- 27. The hypermedia constraint?
- 28. The hypermedia constraint A URI request returns all valid state changes
- 29. The hypermedia constraint It’s how the web works
- 30. The hypermedia constraint You already understand it!
- 31. HTTP
- 32. HTTP Your browser speaks the language of text/html
- 34. <!DOCTYPE html>
- 35. HTML Using hypermedia on the web, you can link to different types of data
- 36. HTML Using hypermedia on the web, you can link to different types of data text/css image/png audio/mpeg
- 37. Hypermedia Types “Hypermedia Types are MIME media types that contain native hyper-linking semantics that induce application flow.” - Mike Amundsen (2010)
- 38. The hypermedia constraint The client tells the server what language it speaks
- 39. The hypermedia constraint The server tells the client what to do
- 40. HTTP/1.1
- 41. HTTP/1.1 HEAD GET POST PUT DELETE TRACE OPTIONS CONNECT PATCH
- 42. GET and POST is OK
- 43. GET and POST is OK REST doesn’t care what methods you use
- 44. GET and POST is OK HTTP cares that the methods are used correctly
- 45. Life in XHTML The website is also the API
- 46. Life in XHTML Inconvenient and difficult to maintain
- 47. False start #1 Attempt a custom hypermedia type
- 48. False start #2 application/atom+xml
- 49. False start #3 application/xhtml+xml
- 50. Custom hypermedia types Consider registered types first
- 51. Custom hypermedia types More likely to be understood
- 53. A solution XHTML has hypermedia controls built in
- 54. A solution Contains most of what I need
- 55. XML based media types Namespaces
- 56. Let’s see it then! @RESTConsole
- 57. What about JSON? application/vnd.collection+json application/hal+json
- 59. Versioning The server makes no assumptions on the capabilities of the client
- 60. Versioning If the client does not support something, it simply ignores it
- 61. Versioning The web is not versioned
- 62. Versioning Correct use of hypermedia means you can change things without affecting clients
- 63. Versioning But if you must...
- 66. http://joind.in/talk/view/3589 @blongden
Editor's Notes
- \n
- \n
- Developer for 20 years\nProfessional developer since 2002\nStarted on C, C++ and Perl\nFocussed on Perl and moved into web app development where I picked up PHP\nmobile web, standards and software architectures\n
- Technical Team Lead since the start of 2010\nOne of the Sheffield office founders\n
- Sole developer of fdrop.it\nCreated to solve my problem of &#x2018;why is it so difficult to send a file to someone online?&#x2019;\n
- \n
- \n
- Doctoral Dissertation\n&#x2018;Architectural Styles and the Design of Network-based Software Architectures&#x2019;\n\none of the principle author of HTTP specification (RFC 1945/2616)\nIn 1999 he was named my MIT Technology Review as one of the top 100 innovators in the world under 35\n\n\n
- \n
- Constraints help to guide the creative project\n\nSacrifice is usually made retroactively\n
- Can be applied to ANY distributed system\nWeb application or API design\n
- \n
- Clients not concerned about data storage\nServers not concerned about the user interface or user state\ncomponents evolve independently if interface remains constant\n
- Each request from the client must contain ALL of the information required\nCannot rely on stored context on the server\nSession state on the client\nVisibility (Server can be observed at any time), Reliability (network failure), Scalability (easy to add servers)\n
- Responses must implicitly or explicitly define themselves as cacheable or not\nFurther improves scalability and performance\n\n
- Client connected to the end server or to an intermediary along the way.\nLoad Balancers\nSecurity Policies at a Firewall\nReverse Proxy Cache\n\n
- Service can temporarily extend client side functionality by providing code it can execute \nie, Javascript or java applets\n\nTHE OPTIONAL CONSTRAINT!\n
- Four guiding principles to simplify architecture\n
- On the web we use URI&#x2019;s\n\nResources themselves are usually different to what is returned to the client\nUsually, a database resource will be represented in JSON or XML\n
- When a client holds a representation, it is enough to be able to modify or delete the resource assuming the user has permission to do so\n
- Each message describes itself. This means using an explicit mime type, and explicitly if the resource can be cached.\n
- Clients make state transitions ONLY through links returned within the resource (ie, anchors in html)\n\nOnly exception is the entry point\n
- HATEOAS is a horrible acronym\n
- Using hypermedia (anchor, xlink, etc)\n
- and it&#x2019;s why it&#x2019;s been so successful over the last 20 years. The web is 20 years old. That&#x2019;s amazing - and because of standards and hypermedia, I can still reference things from 20 years ago.\n
- A web page contains all the information within it to allow the user to move from the current state, to the next.\n
- All types of HTML\nXHTML\n\nVersions within them are identified by the content (DOCTYPE, html tag or xml header)\nXML documents not processed as XML (no checks for well formedness)\n \n
- HTML 5 won over XHTML for who gains supremacy over the browsers - HTML contains some really good stuff about describing text, images, user input etc and what HTTP function to use on them (ie, GET image, POST a form).\n
- This is how you declare an html 5 document. It&#x2019;s great for the web as browsers only need to understand GET and POST - this is fine and it&#x2019;s still RESTful, but what if we need a representation of a resource that can support other actions?\n
- \n
- HTML is a hypermedia type\nXML is not\n
- Accept header in HTTP\n
- HTTP headers and Hypermedia!\n
- \nHTTP 1.1 defines these 9 methods. HTML lets us use 2 of them. \n
- That&#x2019;s all you get in a browser\n\n
- \n
- GET to retrive, POST to create, PUT to update, DELETE\nPOST to a job queue to update and delete\nThese are HTTP, not REST (REST just defines the uniform interface)\n
- API for free?\nDownsides\nSome actions need to be different over an API due to different UI\nAJAX\n
- Focus on the UI breaks the API\n
- Craft my own XML doc\nNeed to define my media type first\nToo much like work...\n
- There was merit to this - which i&#x2019;ll come back to\n
- Remove the markup from the XHTML that was only there to layout the UI\nServe HTML5 to browsers on text/html!\nClose - but webkit on iOS and Android devices prefer XML\n
- \n
- \n
- XHTML still in the media type so still self describing\nWont conflict with browsers\n\n
- \n\n
- form, input, img, a\nBrowsers already understand XHTML\nEasy for people to consume using any XML Reader\nDEMO\n
- XHTML only supports GET and POST\nWhat if we need more?\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n