The Rails Way in 2026
The Rails Way in 2026
We had an interesting discussion at the Arkency weekly call today. The topic was how to define “the Rails Way” in 2026. The discussion branched in many directions, but I want to capture the result here.
We get to see a lot of Rails repositories. There’s a pattern that shows up so consistently that I think it now deserves to be called “the Rails Way” of 2026:
A fat model with a callback. The callback triggers a service object. The service object is executed as a background job.
That’s the clue of this post. If you zoom out across the Rails applications written or maintained in 2026, that’s the shape.
The disclaimer
A word about where we’re coming from. Arkency is a…




Live Demo Available Introducing MapView Render beautiful, production-ready maps directly from your Ruby backend. No external APIs. No dependencies. Just pure speed and control. ✓ Zero external dependencies ✓ Lightning-fast rendering ✓ Production-ready & battle-tested Try … 

Refactoring Databases






See the LIVE DEMO in action MapView Render maps directly from your backend no external APIs required. Fast, controlled, and production-ready. Try the demo → Over the past few months I’ve been working on a small GIS-oriented stack in … 










