The Future of Rack
summary
Covers concrete Rack problems and fixes: shows that 42% of call stack is middleware, demos memory tools (ObjectSpace dumps, allocation_tracer) and reports measured wins — an optimization cuts allocations by about 19% and another tweak yields ~10% improvement — with graphs and code examples. Proposes a new “metal” experimental API on GitHub to replace problematic Rack behaviors (streaming/body proxy, global env keys) and outlines a Rails 5 plan to run tests in parallel by preloading fixtures and coordinating transactions or per-process DBs.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:44Ruby evolution over 10 years
- 10:19Memory profiling tools
- 22:26Rack future and challenges
- 34:52Metal project: new Rack API
- 37:16Rails testing and parallelism
- 45:10Conclusion
- 51:57Q&A
related talks
37mRuby on Rack: The Magic Between Request and Response
28mRack for web developers
38mRewriting Rack: A Functional Approach
48mFrom Rails to Rack: Making Rails 3 a Better Ruby Citizen
41mRack - A Framework to Roll Your Own
48mOn the Edge of Rails Performance
28mIn a World of Middleware, Who Needs Monolithic Applications
30mThe Power of Middleware - Building Your Own Mini Web Framework on Rack
