Is it better than the after_commit_queue [1] gem? Seems like this one is decoupled from model being saved. Which might be expected and desirable or unexpected.
[1] github.com/Ragnarson/after_commit_...
Yes, this gem is better. It uses Active Record APIs (thus, battle-tested) and not a custom queue implementation.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Is it better than the after_commit_queue [1] gem? Seems like this one is decoupled from model being saved. Which might be expected and desirable or unexpected.
[1] github.com/Ragnarson/after_commit_...
Yes, this gem is better. It uses Active Record APIs (thus, battle-tested) and not a custom queue implementation.