RailsRevelry is a focused Substack publication for experienced Rails developers who want clearer mental models of how the framework behaves under the hood. Organized around three key boundaries — the request boundary (Rack, middleware, routing, dispatch), the state boundary between requests (sessions, flash, current_user reconstruction), and the persistence boundary (Active Record, transactions, callback timing) — it aims to help developers locate where behavior actually lives when production bugs appear. The core framing is treating Rails as an execution system rather than a collection of features, making it easier to reason about deferred queries, uncommitted transactions, stale objects, and state that crosses request boundaries.
Table of contents
Rails as an execution system #The request boundary #State, identity, and the space between requests #The persistence boundary #Why make it separate? #90 Impressions