Recently I've released a new gem–Isolator, which helps to detect non-database side effects during a database transaction.
Here is a quick example ...
For further actions, you may consider blocking this person and/or reporting abuse
@andy this seems like something to bookmark for possible use in the future.
This is some next level Ruby stuff. Definitely a great use case! Thanks for the post.
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.
I've extracted this into the gem: github.com/Envek/after_commit_ever...
Cool gem!