October 29, 2019

Taming Large Rails Applications with Private ActiveRecord Models

Hello Folks!

This week’s post follows a similar theme of many previous talks and posts: How can we wrangle large Rails applications?

As a business scales and adds more engineers, some of the Rails defaults start to become difficult to work with. Putting everything in the app/ folder stops being the best idea.

We’ve been exploring a novel pattern at work, which is to declare ActiveRecord models private. This helps better define how to interact with data and can prevent the Ball of Mud.

This is a method of scaling a Rails application without needing to break things out into engines or microservices.

Enjoy!

Taming Large Rails Applications with Private ActiveRecord Models

Until next time,

Kelly