Rails Sojourn: One Man's Journey
summary
A monthlong incubation builds an Airbrake‑style exception service with a Sinatra API and Angular frontend, but the team overengineers into three ORMs before settling on ActiveRecord and splits work across eight repositories. Middleware handles CORS, security and standardized error responses; Vagrant and a tiny console script make local development bearable. The experiment demystifies Rails internals and source digging and concludes that next time Rails API would have been the faster, simpler choice.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 1:53Motivations for the experiment
- 4:52Technology selection
- 9:08Initial architectural hurdles
- 14:01The value of open source
- 18:07Leveraging Rack middleware
- 22:27Tooling and productivity
- 25:05Reflections and lessons
related talks
16mOne Ruby App to Rule Them All
41mOff the Tracks - Challenging the Rails Mindset
37mHow I Architected My Big Rails App For Success
01h 09mRails 3 ...and the real secret to high productivity
32mImplementing Rails 3.1...
23mRails Frontend Evolution: It Was a Setup All Along
42mWeb API's with ERLANG a Ruby Dev's POV
42mBuilding Better Web APIs with Rails