3 ms·
I think it's shipping with its own background processor, Active Jobs. Sounds good!
by ragecore 12y ago
I think it's shipping with its own background processor, Active Jobs. Sounds good!
- bherms 12y agoActiveJob is in 4.2 http://edgeguides.rubyonrails.org/4_2_release_notes.html#active-job http://edgeguides.rubyonrails.org/4_2_release_notes.html#act... http://edgeguides.rubyonrails.org/active_job_basics.html http://edgeguides.rubyonrails.org/active_job_basics.html
- r-s 12y agoActive Jobs, at least how implemented in 4.2 is not its own background processor. Its just a common api for using the background processor of your choice (Sidekiq, Resque, Delayed job etc).
- bherms 12y agoActievJob actually does default to :inline, which uses the Rails process to execute the job, so in a way, it kind of is it's own background processor, but you can easily swap out, as it implements an API for creating and scheduling jobs.