When David Heinemeier Hansson started talking about REST in 2006, little could we suspect it'd become such a central part of Rails (and of web development in general). Back then a web service meant something you coded using XML and SOAP. Those were dark times. REST changed it all.
In this talk, I'll explain REST for beginners, I'll talk about why it is such an important architecture, and I'll show all the nice things Rails offers you for building a RESTful application or a RESTful API.
52. Resources are not models
Don't expose your implementation details
tips on routes
53. Easier to understand
Change the internals
without breaking the
contract
Resources based on
business objects are
more resistant to
versioning
More opacity means
more security
56. huddle
200 OK
201 Created
202 Accepted
400 Bad Request
401 Unauthorized
403 Forbidden
404 Not Found
410 Gone
twitter
200 OK Success!
304 Not Modified
400 Bad Request
401 Unauthorized
403 Forbidden
404 Not Found
406 Not Acceptable
420 Enhance Your Calm
500 Internal Server Error
502 Bad Gateway
503 Service Unavailable
Useful Status
429 Too many requests
204 No Content
teowaki
200 OK Success!
201 Created
304 Not Modified
401 Unauthorized
403 Forbidden
404 Not Found
422 Unprocessable Entity
406 Not Acceptable
500 Internal Server Error
66. Find related links at:
https://teowaki.com/teams/javier-community/link-categories/rest
Thank you
Javier Ramírez
@supercoco9
https://airpair.me/javier
teowaki is the place to share
links, best practices,
documentation, gossip and
lifehacks with other developers.