What is REST? Why is it Part of the Rails Way?
summary
Claims Rails made REST mainstream around 2006 and that REST is simply HTTP plus resources = URLs, representations = JSON/HTML and metadata. Shows a working Rails app (teowaki.com) built “totally restful,” uses routes/resources, controllers with respond_to and headers, Jbuilder for JSON, and recommends Roar for hypermedia links. Demonstrates nesting vs members, status codes like 201/202, and argues resources should reflect public names not one-to-one DB models, which keeps APIs stable and versionable.
AI-written summary · about
chapters (16)
- 0:00Introduction to REST
- 1:06Evolution of Web Services
- 3:25The Problem with SOAP
- 5:32The Rise of REST
- 7:21History and Definition
- 9:53Core REST Principles
- 12:11Resources and Representations
- 16:24HTTP Operations
- 18:39REST in Rails Routing
- 20:55Members and Nesting
- 24:37Naming Conventions
- 26:11Abstraction and Flexibility
- 28:36Controller Implementation
- 31:11Metadata and Templates
- 33:37Why Use REST
- 35:31Hypermedia and Conclusion
related talks
36mIn Relentless Pursuit of REST
31mCRUD is not REST - Hypermedia for Y'All!
50mThe Fashion for REST - Creating Beautiful APIs
52mREST: I don't Think it Means What You Think it Does
42mLet’s Have Some Effective REST!
33mRails is Just Ruby
46mLet’s have some effective REST!
26mNot Invented Here: Things Rails Didn't Innovate