REST, Rails, and APIs: A Guide to Building RESTful Services
•
6 gostaram•1,728 visualizações
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.
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (17)
Destaque
Destaque (7)
Semelhante a REST, Rails, and APIs: A Guide to Building RESTful Services
Semelhante a REST, Rails, and APIs: A Guide to Building RESTful Services (20)
Mais de javier ramirez
Mais de javier ramirez (20)
Último
Último (20)
REST, Rails, and APIs: A Guide to Building RESTful Services
- 1. What is REST? Why is it part of the rails way? javier ramirez @supercoco9
- 2. 20 years ago
- 6. 15 years ago
- 7. the web of portals
- 10. Screen Scrapping
- 12. SOAP Services
- 25. REST is an architecture for the web Roy Fielding's PHD Dissertation. 2000
- 26. REST & RAILS
- 28. Client – server Stateless Cacheable Multi-layered REST constraints. HTTP basics
- 29. uniform interface* REST constraints. The good parts * Convention over configuration FTW
- 31. resource: Anything that can be named uniform interface
- 34. uniform interface: representations. HTML
- 35. uniform interface: representations. JSON
- 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
- 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. But very important tips on routes
- 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
- 54. Rest in Rails: controllers. Basic actions
- 55. respond_to & format Rest in Rails: controllers
- 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
- 57. Rest in Rails: controllers. headers
- 58. representations Rest in Rails: views. templates
- 59. But I'm not building an API. Do I need REST?
- 61. API pagination
- 63. Several resources in a single request
- 65. RESTful web service/application client-server,stateless,layered,cacheable Resources Resource Identifiers Uniform interface operations Representations Metadata Hypermedia
- 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.