Download as PDF, PPTX
Uploaded byjavier ramirez
What is rest. Why is it part of the Rails way?. Railsconf 2014. Javier Ramirez
REST is an architectural style for the web, defined by Roy Fielding's dissertation, emphasizing stateless and cacheable client-server interactions. It is a foundational aspect of Ruby on Rails, promoting a uniform interface for resources identified by URIs, facilitating standard HTTP methods like GET and POST. The document discusses REST principles as applied in Rails, providing guidelines on routing, resource representation, and response handling.
More Related Content
Similar to What is rest. Why is it part of the Rails way?. Railsconf 2014. Javier Ramirez
![[2015/2016] The REST architectural style](https://cdn.slidesharecdn.com/ss_thumbnails/06crest-160429194845-thumbnail.jpg?width=640&height=640&fit=bounds)
![20260201 [FOSDEM] gomodjail - library sandboxing for Go modules.pdf](https://cdn.slidesharecdn.com/ss_thumbnails/20260201fosdemgomodjail-librarysandboxingforgomodules-260201225659-76609ec4-thumbnail.jpg?width=640&height=640&fit=bounds)
What is rest. Why is it part of the Rails way?. Railsconf 2014. Javier Ramirez
- 1. What is REST? Whyis it part of the rails way? javier ramirez @supercoco9
- 2.
- 6.
- 7. the web ofportals
- 8.
- 10.
- 12.
- 18.
- 23.
- 24.
- 25. REST is an architecture forthe web Roy Fielding's PHD Dissertation. 2000
- 26.
- 27.
- 28. Client – server Stateless Cacheable Multi-layered RESTconstraints. HTTP basics
- 29. uniform interface* REST constraints. Thegood parts * Convention over configuration FTW
- 30.
- 31. resource: Anything that can benamed uniform interface
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38. uniform interface: transfer.GET (no id)
- 39. uniform interface: transfer.POST (no id)
- 40. uniform interface: transfer.GET (with id)
- 41. uniform interface: transfer.DELETE (with id)
- 42. HTTP as usual+ resources representations metadata So REST is basically
- 43.
- 44. Rest in Rails:basic routes
- 45. Rest in Rails:advanced routes
- 46. Rest in Rails:advanced routes
- 47. Rest in Rails:members and collections
- 48. tips on routes:don't overload GET /users/1-javier/messages get :messages on: :member
- 49. tips on routes:don't overload GET /users/1-javier/messages POST /users/1-javier/messages get :messages on: :member post :messages on: :member
- 50. tips on routes:don't overload GET /users/1-javier/messages POST /users/1-javier/messages members? No.
- 51. Naming is hard. Butvery important tips on routes
- 52. Resources are notmodels Don't expose your implementation details tips on routes
- 53. Easier to understand Changethe internals without breaking the contract Resources based on business objects are more resistant to versioning More opacity means more security
- 54. Rest in Rails:controllers. Basic actions
- 55. respond_to & format Restin Rails: controllers
- 56. huddle 200 OK 201 Created 202Accepted 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
- 57. Rest in Rails:controllers. headers
- 58. representations Rest in Rails:views. templates
- 59. But I'm not buildingan API. Do I need REST?
- 60.
- 61.
- 62.
- 63. Several resources ina single request
- 64.
- 65. RESTful web service/application client-server,stateless,layered,cacheable Resources ResourceIdentifiers Uniform interface operations Representations Metadata Hypermedia
- 66. Find related linksat: 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.