dry-transaction
packwerk
dry-transaction | packwerk | |
---|---|---|
2 | 16 | |
463 | 1,500 | |
0.0% | 2.1% | |
6.4 | 7.0 | |
4 months ago | 3 days ago | |
Ruby | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dry-transaction
-
Introducing StepSequencer: A Non-Monadic Take on Railway-Oriented Programming in Ruby
While there are other libraries out there like Dry-Transaction and Interactor, StepSequencer stands out in its simplicity and flexibility. Here's why:
-
OOP vs. services for organizing business logic: is there a third way?
dry-transaction
packwerk
-
Must-have gems for mature Rails
gem "packwerk" - https://github.com/Shopify/packwerk | Allows modularising Ruby code, a must-have for growing projects.
-
Keep the Monolith, but Split the Workloads
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
-
All you need is Rails (Engines): Compartmentalising your Monolith
Iād probably go with packwerk before rails engines these days
-
How to break up a rails monolith
https://github.com/Shopify/packwerk allows you to make dependencies between components explicit
- Best way to go about fragmenting a Monolithic Rails application into Microservices.
-
OOP vs. services for organizing business logic: is there a third way?
Packwerk ā to enforce boundaries and modularize Rails applications
-
Organizing Rails files by meaning
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.
-
How to edit a model from another controller
Nothing is stopping you from doing so except you (and maybe packwerk, but you very likely don't have that installed).
-
The advent of tooling for Big Rails
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.
-
Exploring DryRB - Intuition of Results
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.
What are some alternatives?
Interactor - Interactor provides a common interface for performing complex user interactions.
Solidus - š Solidus, the open-source eCommerce framework for industry trailblazers.
Trailblazer - The advanced business logic framework for Ruby.
appmap-ruby - AppMap client agent for Ruby
Waterfall - A slice of functional programming to chain ruby services and blocks, thus providing a new approach to flow control. Make them flow!
django-rq - A simple app that provides django integration for RQ (Redis Queue)
SimpleCommand - A simple, standardized way to build and use Service Objects (aka Commands) in Ruby
whitehall - Publishes government content on GOV.UK
Rails Event Store - A Ruby implementation of an Event Store based on Active Record
suture - š„ A Ruby gem that helps you refactor your legacy code
Cells - View components for Ruby and Rails.
gitlab