Building in Rails, Backbone, and CoffeeScript
summary
Rails back end serves the same JSON API to web, mobile and desktop; Backbone + CoffeeScript handles models, collections and atomic views with a view manager to avoid memory leaks. Real-time uses ejabberd XMPP with Strophe.js and a pre-authenticated BOSH stream (Ruby BOSH) to cut auth to one round trip. Server caches aggressively (memcached, action cache, Rabl + fragment/Russian-doll caching keyed on updated_at and count) so an inbox of 20 deliveries answers in about 100 ms average response. Client assumes success for immediate UI updates and rolls back on error.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:04Web trends and frameworks
- 2:29Kicksend technology stack
- 5:31Backend and API design
- 8:08Front-end structure
- 10:23Rendering and view management
- 12:32Performance optimization
- 13:56Caching strategies
- 18:35Perceived performance
- 21:06Real-time functionality
- 23:25Conclusion and Q&A
related talks
29mBackbone.js, Jasmine and Rails: The Lust Story
07mBuilding Real-Time App with React/Redux/Rails/RethinkDB
40mUsing Backbone.js with Rails: Patterns from the Wild
29mBackbone.js, Jasmine and Rails: The Lust Story
24mBuilding Realtime Singlepage Apps
29mRealtime web applications with streaming REST
23mImplications of the Realtime Web
38mHigh Concurrent Ruby Web Development Without Fear