ActionCable, Rails API and React - Modern Single Page Apps
summary
Rails 5 claims to pair a slimmed Rails API backend with ActionCable WebSockets to power modular SPAs; the demo shows a Rails API app (API-only controllers, ActiveRecord) broadcasting comment payloads via Redis adapter and Puma for concurrent connections to a separate Node/React client, where a React + Redux component receives updates and updates state automatically. The build is a working realtime message/comment flow across Rails and a standalone React app, not just theoretical.
AI-written summary · about
chapters (21)
- 0:00Start
- 1:32Second time in Taiwan
- 6:24Rails 5
- 7:32What is an API Application?
- 9:33Why Rails?
- 12:06AP Sweetness
- 13:06Lets create chatty
- 13:38What this does
- 14:59Default Stack
- 15:35Action Controller::API
- 17:09What is Action Cable?
- 19:06Concepts
- 20:31Server Side
- 20:58Connections
- 22:30Channels
- 23:14Consumer Connection
- 25:15Tying them up together
- 25:34Streams
- 27:51Client Side Subscription
- 30:17Somethings to take care of
- 33:16A Simple Component
related talks
31mReact.js on Rails
07mBuilding Real-Time App with React/Redux/Rails/RethinkDB
25m"React integration into existing Rails applications"
39mActionCable for Not-Another-Chat-App-Please
36mFront-End Sadness to Happiness: The React on Rails Story
31mReact on Rails
18mReact-ing to Rails: Why Ruby on Rails is the best Stop for Web Developer
28mBack to React: The Story of Two Apps