packwerk VS appmap-ruby

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.

AppMap currently supports Ruby, Java, Python, and Javascript projects and the libraries are MIT licensed.

Yes, sure. I've added a link to the docs above, and the repo is here - https://github.com/applandinc/appmap-ruby

Well, I’m definitely biased, but we welcome devs at all XP levels at the appmap project. Take a look. If you can’t find a good first issue @ Dan, Dustin, Kevin, or Petr in the Discord and someone will hook you up. https://github.com/applandinc/appmap-ruby We have needs from doc to core features!

In order to help make this a reality, we have created the open source AppLand Framework. The AppLand Framework includes components to:

AppLand is an open source framework that developers can use to record, analyze, and optimize end-to-end code and data flows. The framework provides client agents for Ruby, Java and Python (beta) that record running code and generate JSON files called AppMaps. Users can view and analyze AppMaps locally using the AppMap extension for VS Code, and also push AppMaps to the AppLand server for analytics, sharing, discussion etc.

Now, what if you want to be able to efficiently fetch a subset of JSONB data, without having to load and parse every object? At AppLand, we store AppMap data in the database. Each AppMap has a mandatory section called metadata, and we want to be able to efficiently pull out the metadata of selected rows without having to parse the entire JSONB column (the metadata is usually less than 1% of the total JSON object). Awesomely, since PostgreSQL 12, PostgreSQL has a feature called generated columns.

Install the appmap gem by following the instructions in the README. Here's a quick checklist:

[3] AppLand framework, a tool to record, display, and analyze end-to-end code and data flows.