awesome-rails VS packwerk

There are also plenty of other resources that might be of use, like the awesome rails collection.

https://github.com/gramantin/awesome-rails has a large list of varying quality

There’s a curated list of Open Source Rails Apps. - Not sure how many of these are modularized into engines.

This seems interesting: https://github.com/gramantin/awesome-rails

- Code code code, use codewars.com for challenges in ruby, ask questions on the discord and discourse and try to help others, and maybe look at some Open Sourece projects in rails to get a sense of a small project compared to a massive project in rails. You can find all kinds of exampels here: https://github.com/gramantin/awesome-rails

gem "packwerk" - https://github.com/Shopify/packwerk | Allows modularising Ruby code, a must-have for growing projects.

Yep, that article is about very similar concepts but grounded in Spring as the framework.

I like what they do around package imports and it looks a lot like what we do at incident.io, with some rules about which packages can import what.

For people in the Ruby world who want a similar solution, Shopify provide an open-source framework called packwerk that is designed just for this:

https://github.com/Shopify/packwerk

I’d probably go with packwerk before rails engines these days

https://github.com/Shopify/packwerk allows you to make dependencies between components explicit

Packwerk – to enforce boundaries and modularize Rails applications

Take a look at Packwerk from some folks at Shopify - gets you the benefits of naming some components for organizing boundaries in your code, with each component having the usual rails folder structure, but without the hard isolation restrictions of doing so with Engines.

Nothing is stopping you from doing so except you (and maybe packwerk, but you very likely don't have that installed).

For me, the most important aspect of a growing Rails app is handling of complexity and interdependencies and turns out Shopify's packwerk is just what the doctor ordered - it leverages zeitwerk loader to improve on Rails' vanilla file structure, allowing to group files by business concept or sub-domain and control visibility and ownership.

Let's set the stage right quick. You happen to be in a large Rails application that follows along with something like Packwerk to clearly delineate different packages in your Rails monolith. Let's say you have 100 packs, which is not particularly unusual with larger applications.