In a World of Middleware, Who Needs Monolithic Applications
summary
Claim: replacing monolithic Rails code with Rack middleware yields composable services. Concrete examples: Rack apps implement call and return [status, headers, body] and rack-lint enforces the spec; cloudkit exposes notes and to-dos and mounts REST endpoints while uses Tokyo Cabinet as storage; an OAuth filter and OpenID filter cooperate via environment flags and pseudo via arrays to handle browser and service flows; Sinatra can be used as middleware and Rails can mount middleware via config.use.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 1:03Who am I
- 1:25Solo Platform
- 2:44Pearl CGI
- 4:00Monolithic Apps
- 5:57Web Architecture
- 6:25Rack
- 7:20Rack App
- 8:14Rack Up
- 8:27Lambda
- 8:43RackLint
- 9:31Request Methods
- 9:43Accept Headers
- 9:58Rack Input
- 11:23Middle
- 12:49Rack Profiles
- 13:11Rack CSS HTTP
- 14:20Rack Not Found
- 15:16Cooperative Middleware
- 15:37Cloudkit
- 16:28RackBuilder
- 16:52OAuth Filter
- 19:04HTTP via headers
- 20:24Rackmap
- 21:07Sinatra App
- 21:58Sinatra middleware
- 22:11Rack Cascade
- 22:38Sinatra for Rails
- 23:21CloudKid for Rails
- 24:16Questions
- 26:59DD Admin
related talks
22mRack Middleware as a General Purpose Abstraction
33mRack Middleware as a General Purpose Abstraction
30mThe Power of Middleware - Building Your Own Mini Web Framework on Rack
28mRack for web developers
27mHarness the power of functions to build composable rack applications
37mRuby on Rack: The Magic Between Request and Response
41mRack - A Framework to Roll Your Own
48mFrom Rails to Rack: Making Rails 3 a Better Ruby Citizen