Ben Ramsey • Zend/PHP Conference & Expo • 4 Nov 2010
Grokking REST
What is REST?
#webdevgangsign
Representational State Transfer
Client-server
Stateless
Cache
Uniform Interface
Layered System
Code-on-demand
RESTful Concepts
Resources & URLs
URLs do not matter
Using URLs as interfaces
creates tight coupling
between the client & server
http://api.example.org/user/getUser?u=ramsey
Using URL templates creates
tight coupling between the
client & server
http://api.example.org/user/{username}/photos
Your hypermedia format
should expose the URLs that
represent your resources
<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom"
xml:base="http://atom.example.org/">
<ti...
Hypermedia
application/json
{
"id": "756315701",
"name": "Ben Ramsey",
"first_name": "Ben",
"last_name": "Ramsey",
"link": "http://www.facebook.com/ra...
Hypermedia?
No.
application/facebook+json;
type=user
application/xml
<?xml version="1.0" encoding="utf-8"?>
<user>
<id>756315701</id>
<name>Ben Ramsey</name>
<first_name>Ben</first_name>
<las...
Hypermedia?
No.
application/facebook+xml;
type=user
application/xhtml+xml
Hypermedia?
Yes!
application/atom+xml
Hypermedia?
Yes!
HATEOAS
Grokking REST • Ben Ramsey
‣How does a client know what to do with resources?
‣How do you go to the “next” operation?
‣Wha...
Grokking REST • Ben Ramsey
Hypermedia as the Engine of Application
State (HATEOAS)
‣Use links to allow clients to discover...
Why is REST so great?
REST scales
It’s extensible
It’s evolvable
Grokking REST • Ben Ramsey
Accept: application/vnd.myservice+xml;version=2
Use this style for versioning
47
Grokking REST • Ben Ramsey
http://api.example.org/v2/foo
Not this style
48
Grokking REST • Ben Ramsey
Accept:
application/vnd.mytype+xml;version=1;q=0.5,
application/vnd.myservice+xml;version=2
Cli...
It’s seamless
Atom
Entry Document
application/atom+xml;type=entry
Feed/Collection Document
application/atom+xml
Category Document
application...
GET	
  /	
  HTTP/1.1
Host:	
  atom.example.org
Accept:	
  application/atomsvc+xml,	
  application/atomcat+xml,	
  applicat...
GET	
  /user	
  HTTP/1.1
Host:	
  atom.example.org
Accept:	
  application/atom+xml
HTTP/1.x	
  200	
  OK
Date:	
  Mon,	
  ...
GET	
  /cat/user	
  HTTP/1.1
Host:	
  atom.example.org
Accept:	
  application/atomcat+xml
HTTP/1.x	
  200	
  OK
Date:	
  M...
POST	
  /user	
  HTTP/1.1
Host:	
  atom.example.org
Content-­‐Type:	
  application/atom+xml;type=entry
<?xml	
  version="1...
Bringing it all together…
Grokking REST • Ben Ramsey
Questions?
‣I blog at benramsey.com.
‣I tweet at @ramsey.
‣Please rate this presentation at joi...
Grokking REST
Copyright © 2010 Ben Ramsey. Some rights reserved.
Presented on November 4, 2010 at Zend/PHP Conference
and ...
Grokking REST • Ben Ramsey
Photo Credits
‣ Restful Summer, by Clear Inner Vision
‣ Roatan Beach - Perfect Day, by Janusz
L...
Grokking REST • Ben Ramsey
Photo Credits
‣ Molecule display, by Christian Guthier
‣ Conclusion, by Mark Cummins
61
Grokking REST (ZendCon 2010)
Grokking REST (ZendCon 2010)
Grokking REST (ZendCon 2010)
Upcoming SlideShare
Loading in...5
×

Grokking REST (ZendCon 2010)

2,858

Published on

REST has become a hip buzzword of Web 2.0. But what makes an application RESTful? In this talk, Ben Ramsey reintroduces REST, uncovering each constraint that forms REST's principles. Ramsey explains how REST is a style for network-based software applications, emphasizing scalability and efficiency through separation of concerns and taking advantage of the Web as a platform for rich applications.

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,858
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
71
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Grokking REST (ZendCon 2010)

  1. 1. Ben Ramsey • Zend/PHP Conference & Expo • 4 Nov 2010 Grokking REST
  2. 2. What is REST?
  3. 3. #webdevgangsign
  4. 4. Representational State Transfer
  5. 5. Client-server
  6. 6. Stateless
  7. 7. Cache
  8. 8. Uniform Interface
  9. 9. Layered System
  10. 10. Code-on-demand
  11. 11. RESTful Concepts
  12. 12. Resources & URLs
  13. 13. URLs do not matter
  14. 14. Using URLs as interfaces creates tight coupling between the client & server
  15. 15. http://api.example.org/user/getUser?u=ramsey
  16. 16. Using URL templates creates tight coupling between the client & server
  17. 17. http://api.example.org/user/{username}/photos
  18. 18. Your hypermedia format should expose the URLs that represent your resources
  19. 19. <?xml version="1.0" encoding="utf-8"?> <entry xmlns="http://www.w3.org/2005/Atom" xml:base="http://atom.example.org/"> <title>ramsey</title> <author> <name>ramsey</name> </author> <link rel="self" href="user/ramsey"/> <link rel="edit" type="application/atom+xml;type=entry" href="user/ramsey"/> <link rel="related" href="user/ramsey/content"/> <id>tag:example.org,2008:user/ramsey</id> <updated>2009-09-21T13:45:00Z</updated> <published>2008-05-23T16:23:34Z</published> <content type="xhtml"> <div class="vcard" xmlns="http://www.w3.org/1999/xhtml"> <a class="fn">Ben Ramsey</a> <span class="tel">123-456-7890</span> </div> </content> </entry>
  20. 20. Hypermedia
  21. 21. application/json
  22. 22. { "id": "756315701", "name": "Ben Ramsey", "first_name": "Ben", "last_name": "Ramsey", "link": "http://www.facebook.com/ramseyben", "gender": "male", "locale": "en_US" }
  23. 23. Hypermedia?
  24. 24. No.
  25. 25. application/facebook+json; type=user
  26. 26. application/xml
  27. 27. <?xml version="1.0" encoding="utf-8"?> <user> <id>756315701</id> <name>Ben Ramsey</name> <first_name>Ben</first_name> <last_name>Ramsey</last_name> <link>http://www.facebook.com/ramseyben</link> <gender>male</gender> <locale>en_US</locale> </user>
  28. 28. Hypermedia?
  29. 29. No.
  30. 30. application/facebook+xml; type=user
  31. 31. application/xhtml+xml
  32. 32. Hypermedia?
  33. 33. Yes!
  34. 34. application/atom+xml
  35. 35. Hypermedia?
  36. 36. Yes!
  37. 37. HATEOAS
  38. 38. Grokking REST • Ben Ramsey ‣How does a client know what to do with resources? ‣How do you go to the “next” operation? ‣What are the URLs for creating subordinate resources? ‣Where is the contract for the service? 41
  39. 39. Grokking REST • Ben Ramsey Hypermedia as the Engine of Application State (HATEOAS) ‣Use links to allow clients to discover locations and operations ‣Link relations are used to express the possible options ‣Clients do not need to know URLs, so they can change ‣The entire application workflow is abstracted, thus changeable ‣The hypermedia type itself can be versioned if necessary ‣No breaking of clients if the implementation is updated! 42
  40. 40. Why is REST so great?
  41. 41. REST scales
  42. 42. It’s extensible
  43. 43. It’s evolvable
  44. 44. Grokking REST • Ben Ramsey Accept: application/vnd.myservice+xml;version=2 Use this style for versioning 47
  45. 45. Grokking REST • Ben Ramsey http://api.example.org/v2/foo Not this style 48
  46. 46. Grokking REST • Ben Ramsey Accept: application/vnd.mytype+xml;version=1;q=0.5, application/vnd.myservice+xml;version=2 Clients can specify preferences 49
  47. 47. It’s seamless
  48. 48. Atom
  49. 49. Entry Document application/atom+xml;type=entry Feed/Collection Document application/atom+xml Category Document application/atomcat+xml Service Document application/atomsvc+xml
  50. 50. GET  /  HTTP/1.1 Host:  atom.example.org Accept:  application/atomsvc+xml,  application/atomcat+xml,  application/atom+xml HTTP/1.x  200  OK Date:  Mon,  21  Sep  2009  16:33:45  GMT Content-­‐Type:  application/atomsvc+xml <?xml  version="1.0"  encoding="utf-­‐8"?> <service  xmlns="http://www.w3.org/2007/app"                  xmlns:atom="http://www.w3.org/2005/Atom"                  xml:base="http://atom.example.org/">  <workspace>    <atom:title>Our  Content  Store</atom:title>    <collection  href="user">      <atom:title>Users</atom:title>      <accept>application/atom+xml;type=entry</accept>      <categories  href="cat/user"/>    </collection>    <collection  href="content">      <atom:title>Content</atom:title>      <accept>application/atom+xml;type=entry</accept>      <categories  href="cat/content"/>    </collection>  </workspace> </service>
  51. 51. GET  /user  HTTP/1.1 Host:  atom.example.org Accept:  application/atom+xml HTTP/1.x  200  OK Date:  Mon,  21  Sep  2009  16:34:26  GMT Content-­‐Type:  application/atom+xml <?xml  version="1.0"  encoding="utf-­‐8"?> <feed  xmlns="http://www.w3.org/2005/Atom"            xmlns:app="http://www.w3.org/2007/app"            xml:base="http://atom.example.org/">  <title>Users</title>  <updated>2009-­‐09-­‐21T05:21:19Z</updated>  <id>tag:example.org,2009-­‐09:user</id>  <app:collection  href="user">    <title>Users</title>    <app:accept>application/atom+xml;type=entry</app:accept>    <app:categories  href="cat/user"/>  </app:collection>  <link  rel="first"  href="user"/>  <link  rel="last"  href="user?p=23"/>  <link  rel="next"  href="user?p=2"/>  <entry>    ...  </entry> </feed>
  52. 52. GET  /cat/user  HTTP/1.1 Host:  atom.example.org Accept:  application/atomcat+xml HTTP/1.x  200  OK Date:  Mon,  22  Sep  2009  09:39:26  GMT Content-­‐Type:  application/atomcat+xml <?xml  version="1.0"?> <app:categories      xmlns:app="http://www.w3.org/2007/app"    xmlns:atom="http://www.w3.org/2005/Atom"    fixed="yes"      scheme="http://atom.example.com/cat/user">  <atom:category  term="manager"/>  <atom:category  term="team"/>  <atom:category  term="user"/> </app:categories>
  53. 53. POST  /user  HTTP/1.1 Host:  atom.example.org Content-­‐Type:  application/atom+xml;type=entry <?xml  version="1.0"  encoding="utf-­‐8"?> <entry  xmlns="http://www.w3.org/2005/Atom"              xml:base="http://atom.example.org/">  <title>ramsey</title>  <author>    <name>ramsey</name>  </author>  <id>tag:example.org,2008:user/ramsey</id>  <published>2008-­‐05-­‐23T16:23:34Z</published>  <content  type="xhtml">      <div  class="vcard"  xmlns="http://www.w3.org/1999/xhtml">        <a  class="fn">Ben  Ramsey</a>        <span  class="tel">123-­‐456-­‐7890</span>      </div>  </content> </entry> HTTP/1.x  201  Created Date:  Mon,  22  Sep  2009  09:39:26  GMT Location:  http://atom.example.org/user/ramsey Content-­‐Type:  text/html <html> <body>    <p>Your  new  resource  was  created          <a  href="http://atom.example.org/user/ramsey">here</a>.</p> </body> </html>
  54. 54. Bringing it all together…
  55. 55. Grokking REST • Ben Ramsey Questions? ‣I blog at benramsey.com. ‣I tweet at @ramsey. ‣Please rate this presentation at joind.in/2284. ‣Find out more about REST by reading Architectural Styles and the Design of Network-based Software Architectures and “How I Explained REST to my Wife.” ‣My company is Moontoast. Check us out at moontoast.com. Follow us on Twitter and like us on Facebook. 58
  56. 56. Grokking REST Copyright © 2010 Ben Ramsey. Some rights reserved. Presented on November 4, 2010 at Zend/PHP Conference and Expo, Hyatt Regency Hotel, Santa Clara, CA. This work is licensed under a Creative Commons Attribution- Noncommercial-No Derivative Works 3.0 United States License. For uses not covered under this license, please contact the author.
  57. 57. Grokking REST • Ben Ramsey Photo Credits ‣ Restful Summer, by Clear Inner Vision ‣ Roatan Beach - Perfect Day, by Janusz Leszczynski ‣ Tom Coates, by Patrick Lauke ‣ Web Developer Gang Sign, by Josh Lewis ‣ A Bar of Ivory Soap, by iirraa ‣ Albert Einstein, Public Domain, from Wikimedia Commons ‣ Separated, by Hansol Lee ‣ Stateless by Koesmanto Bong ‣ Cache County, Utah by J. Stephen Conn ‣ used to interface, by Tom Hensel ‣ Sedimentary Layers by Mark Thurman ‣ jeremy’s tie by Gitchel ‣ Sand Banks Sunset, by Clear Inner Vision ‣ Where I Teach, by Todd Ehlers ‣ Frosted Glass door, Goderham Building, by Rick Innis ‣ Drip Drops and the Spider Web, by Mike Bitzenhofer ‣ #110 Hypertext Transfer Protocol, by maako ‣ Before we had CAD, we had Lead!, by Wendell 60
  58. 58. Grokking REST • Ben Ramsey Photo Credits ‣ Molecule display, by Christian Guthier ‣ Conclusion, by Mark Cummins 61
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×