Let's talk about REST

The spiffiness, the sulkiness, the general interestingness of RESTful APIs and their implementation in today's internet.
High level, just a bit of fun really :)

Transcript

1. lets talk about @astromoose
2. mmm, rest
4. sorry
5. get to the point, jon
6. representational state transfer
7. hark, an fla!
8. We all use rest every day
9. get head post put delete trace options connect patch
10. not a standard
11. not a standard corba, rpc, soap are standards.
12. not a standard corba, rpc, soap are standards. and they are also kind of craaaap
13. SOAP: COMPLEX <?xml  version="1.0"?>   <soap:Envelope   xmlns:soap="http://www.w3.org/2001/12/soap-­‐envelope"   soap:encodingStyle="http://www.w3.org/2001/12/soap-­‐encoding">    <soap:body  pb="http://www.acme.com/phonebook">      <pb:GetUserDetails>        <pb:UserID>12345</pb:UserID>      </pb:GetUserDetails>    </soap:Body>   </soap:Envelope>
14. SOAP: COMPLEX <?xml  version="1.0"?>   <soap:Envelope   xmlns:soap="http://www.w3.org/2001/12/soap-­‐envelope"   soap:encodingStyle="http://www.w3.org/2001/12/soap-­‐encoding">    <soap:body  pb="http://www.acme.com/phonebook">      <pb:GetUserDetails>        <pb:UserID>12345</pb:UserID>      </pb:GetUserDetails>    </soap:Body>   </soap:Envelope>
15. REST: SIMPLE http://www.acme.com/phonebook/UserDetails/12345
16. REST: SIMPLE http://www.acme.com/phonebook/UserDetails/12345
17. so, rest apis.
18. so, rest apis. omg ANOTHER TLA lol
20. Get! put! post! delete! st! te! Get po del
21. SEE ALL OF THEse internet WIDGETS GET  http://awesomewidgets.com/api/widgets   ! MAKE me A WIDGET, internet POST  http://awesomewidgets.com/api/widgets   Data:          name  =  smash   ! show me this supposed SINGLE WIDGET WITH ID 123 GET  http://awesomewidgets.com/api/widgets/123   ! UPDATE THAT WIDGET UPDATE IT UPDATE ITTTT PUT  http://awesomewidgets.com/api/widgets/123   Data:          name  =  kaboom          color  =  electric  puce   ! DELETE THAT STUPID WIDGET I MEAN WHAT THE HELL internet DELETE  http://awesomewidgets.com/api/widgets/123
22. jon@raven:~  (ruby-­‐2.0.0-­‐head)   [◦]  %
23. jon@raven:~  (ruby-­‐2.0.0-­‐head)   [◦]  % curl  -­‐i  http://coffee.is.local/rest/players
24. jon@raven:~  (ruby-­‐2.0.0-­‐head)   [◦]  % curl  -­‐i  http://coffee.is.local/rest/players HTTP/1.1  200  OK   Server:  nginx/1.0.11   Date:  Thu,  21  Nov  2013  13:54:06  GMT   Content-­‐Type:  application/json   Connection:  keep-­‐alive   vary:  Accept-­‐Encoding   content-­‐length:  3312   ! [{"_id":"ce185d9a-­‐6e8f-­‐4f82-­‐af52-­‐4f104652c38d","etab":18,"ltab": 0,"name":"Silvia","total":414},{"_id":"799e8aa0-­‐ b346-­‐48ee-­‐8d7f-­‐756d68d34de2","etab":34,"ltab": 1,"name":"Javier","total":481}, {"_id":"c9909966-­‐6d79-­‐4bce-­‐9b46-­‐9a995bbf01b3","etab":4,"ltab":
25. What happens when aN API request goes wrong?
26. handily What happens when aN API request goes wrong?
27. handily http has a whole bunch of very well understood status codes What happens when aN API request goes wrong?
28. 4xx error 5xx error means i messed up means you guys messed up
29. here comes a bold statement!
30. rest apis are usually great here comes a bold statement!
31. documented & idempotent When they are
33. Twitter thrives on its clients
34. Is there anything wrong with rest?
35. real time sucks.
36. real time sucks. client API anything new? nope.
37. real time sucks. client API anything new? nope. client API How about now? nope.
38. real time sucks. client API anything new? nope. client API How about now? nope. client API And now?? widgets!
39. have big files to worry about
41. The current hip answer?
42. The current hip answer? client API
43. The current hip answer? client API hey hey new widgets!
44. The current hip answer? client API woahhhh hey hey new widgets!
45. The current hip answer? client API woahhhh hey hey new widgets! resthooks
46. POST  http://awesomewidgets.com/api/widgets/hooks   Data:           myApp  =  widgetfu           Callback  =  http://widgetfu.com/api/widgets/track   hipster api
47. i guess you're thinking
48. kthanx jon i guess you're thinking
49. kthanx jon but why should we care? i guess you're thinking
50. go forth and build internet lego
51. restcookbook.com ! apiary.io ! sinatrarb.com ! dev.twitter.com ! developer.github.com ! rest.elkstein.org ! zapier.com
52. CHeerio