An observation from Arkency's consulting work identifies a recurring architectural pattern in Rails codebases in 2026: fat models with callbacks that trigger service objects, which in turn schedule background jobs. Active Record rows increasingly carry mixed responsibilities — entity state, workflow/process state, and auxiliary

5m read timeFrom blog.arkency.com
Post cover image
Table of contents
The disclaimerProcesses and workflows inside Active RecordOne more piece: concernsWhy this matters

Sort: