isolator
ActiveInteraction
| isolator | ActiveInteraction | |
|---|---|---|
| 4 | 6 | |
| 826 | 2,039 | |
| - | - | |
| 6.8 | 2.5 | |
| 5 days ago | 23 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.
isolator
-
Wfolio: professional image processing for professional photographers
In fact, the project had already taken advantage of a number of Evil Martians OSS products, like Autoprefixer, after_commit_everywhere, and isolator.
- O que não fazer ao usar background jobs(baseado em experiência com rails+sidekiq)
-
TIL: Queuing Sidekiq workers safely with the help of Isolator
The first is isolator, a gem by the folks over at Evil Martians that detects non-atomic interactions within a database transaction. What do we mean by that? A simple example taken from the documentation that uses background jobs is something like the following:
-
Rails application boilerplate for fast MVP development
add isolator
ActiveInteraction
-
The Decree Design Pattern
One of the first things I plug into any new or inherited rails project over the last few years is ActiveInteraction.
-
Applying the Use Case Pattern with Rails
The Interactor and ActiveInteraction gems are both great libraries for implementing this pattern.
-
Is there a Gem to help skinny up controllers?
I guess that ActiveInteraction is what you're looking for: https://github.com/AaronLasseigne/active_interaction
-
How does Application Interaction runs 'execute' function?
Skimming the README, it looks like you can pass a lambda as a default:
-
Rails application boilerplate for fast MVP development
active_interaction to make controllers thin
-
How can I ask the controller to ask another controller to call one of its actions? Without violating the SRP?
I prefer building "interactions" these days (specific, single-purpose "services" that are easily callable and composable), using https://github.com/AaronLasseigne/active_interaction
What are some alternatives?
Ahoy - Simple, powerful, first-party analytics for Rails
Interactor - Interactor provides a common interface for performing complex user interactions.
Fasterer - :zap: Don't make your Rubies go fast. Make them go fasterer ™. :zap:
Trailblazer - The advanced business logic framework for Ruby.
after_commit_everywhere - Use ActiveRecord transactional callbacks outside of models, literally everywhere in your application.
Mutations - Compose your business logic into commands that sanitize and validate input.
bullet - help to kill N+1 queries and unused eager loading
Rails Event Store - A Ruby implementation of an Event Store based on Active Record
Traceroute - A Rake task gem that helps you find the unused routes and controller actions for your Rails 3+ app
Light Service - Series of Actions with an emphasis on simplicity.
Sidekiq - Simple, efficient background processing for Ruby
PageletRails - Improve perceived performance of your rails application with minimum effort