Interactor
wisper
Our great sponsors
Interactor | wisper | |
---|---|---|
16 | 6 | |
3,315 | 3,229 | |
0.4% | - | |
0.0 | 1.5 | |
19 days ago | about 2 months 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.
Interactor
-
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:
-
The Decree Design Pattern (Ruby on Rails)
At my current job we use `interactor` which is similar, but simpler, and the precursor to light-service: https://github.com/collectiveidea/interactor
-
Looking for advice on how to do multiple methods depending on params
Thanks for the info. I like the sounds of that article. I think I was sort of thinking along those lines myself but didn't know what to refer to it as. I stumbled on to this as well after reading the article: https://github.com/collectiveidea/interactor.
-
OOP vs. services for organizing business logic: is there a third way?
Interactor
-
How to avoid if/else with different ramifications
You might be looking for an interactor pattern for these services. I've used this gem for similar things before and have had good experiences.
-
Rectify Gem?
FWIW Interactor has only received bugfixes and a single enhancement over the last 4 years: https://github.com/collectiveidea/interactor/blob/master/CHANGELOG.md and before that, the last meaningful change was 8 years ago.
-
SolidService - A service pattern with a simple API
Looks a lot like the Interactor pattern: https://github.com/collectiveidea/interactor
-
What Would be Your Ideal Ruby Tech Stack
I see many senior Ruby developers around me going away from that magicness (like all the validations and callbacks) to move away from fat models, using libs like https://github.com/collectiveidea/interactor and have their own control.
-
Applying the Use Case Pattern with Rails
The Interactor and ActiveInteraction gems are both great libraries for implementing this pattern.
- Utilizando o padrão interactor no Ruby on Rails
wisper
-
Publish/Subscribe with Sidekiq
Wisper: A Ruby gem providing a decoupled communication layer between different parts of an application -> I personally dislike wisper. I used it in the past and dislike the way of defining subscribers in a global way. I wanted topics to be arbitrary and each class to define what to subscribe for itself.
-
OOP vs. services for organizing business logic: is there a third way?
Wisper – the Publish-Subscribe design pattern
-
Event Store with Rails
I haven't used it, but we're also considering it in our app for quite some time. Our main issue is mostly that our codebase is super coupled, especially some older code, and using events as a means of communication between different modules of the app can be nice way of decoupling things. I think this is the most common usecase, and for this you don't necessarily even need to persist the events, and also something like wisper might be useful https://github.com/krisleech/wisper.
-
Rails Google Cloud PubSub options
Whisper (not updated since 2020)
-
How to avoid if/else with different ramifications
I would use events. Every services broadcast its results and everything that needs to listen for them. It also great to decouple dependencies between services. I like the Wisper gem : https://github.com/krisleech/wisper
-
"I'm the CTO of a Growing Rails Startup" Ask Me Anything
We follow the interactor pattern to store our business logic. So we mainly have skinny controllers, skinny models and then interactors. We also don't use ActiveRecord callbacks very much, we primarily use Wisper to broadcast events and then various domains can subscribe to the events they care about and respond accordingly.
What are some alternatives?
ActiveInteraction - :briefcase: Manage application specific business logic.
Rails Event Store - A Ruby implementation of an Event Store based on Active Record
Light Service - Series of Actions with an emphasis on simplicity.
Rocketman - 🚀 Rocketman help build event-based/pub-sub code in Ruby
Trailblazer - The advanced business logic framework for Ruby.
Cells - View components for Ruby and Rails.
dry-transaction - Business transaction DSL
Rectify - Build maintainable Rails apps
Waterfall - A slice of functional programming to chain ruby services and blocks, thus providing a new approach to flow control. Make them flow!
SimpleCommand - A simple, standardized way to build and use Service Objects (aka Commands) in Ruby
Amoeba - A ruby gem to allow the copying of ActiveRecord objects and their associated children, configurable with a DSL on the model