Interactor VS ActiveInteraction

While there are other libraries out there like Dry-Transaction and Interactor, StepSequencer stands out in its simplicity and flexibility. Here's why:

At my current job we use `interactor` which is similar, but simpler, and the precursor to light-service: https://github.com/collectiveidea/interactor

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.

Interactor

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.

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.

Looks a lot like the Interactor pattern: https://github.com/collectiveidea/interactor

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.

The Interactor and ActiveInteraction gems are both great libraries for implementing this pattern.

One of the first things I plug into any new or inherited rails project over the last few years is ActiveInteraction.

The Interactor and ActiveInteraction gems are both great libraries for implementing this pattern.

I guess that ActiveInteraction is what you're looking for: https://github.com/AaronLasseigne/active_interaction

Skimming the README, it looks like you can pass a lambda as a default:

active_interaction to make controllers thin

I prefer building "interactions" these days (specific, single-purpose "services" that are easily callable and composable), using https://github.com/AaronLasseigne/active_interaction