Active Job: Difference between revisions
Jump to navigation
Jump to search
(ychen71@introduction added) |
No edit summary |
||
| Line 2: | Line 2: | ||
Active Job is a framework help developers writing codes and run them on the background automatically under different scenarios. Jobs can vary from schedule newsletter, follow-up emails to database housekeeping. It’s a interface that adapts different queueing backends like Backburner[https://github.com/nesquena/backburner], Delayed Job[https://github.com/collectiveidea/delayed_job], Qu[https://github.com/bkeepers/qu] and so on. [http://guides.rubyonrails.org/4_2_release_notes.html] Overall, Active Job is a interface which you can work with common queues. | Active Job is a framework help developers writing codes and run them on the background automatically under different scenarios. Jobs can vary from schedule newsletter, follow-up emails to database housekeeping. It’s a interface that adapts different queueing backends like Backburner[https://github.com/nesquena/backburner], Delayed Job[https://github.com/collectiveidea/delayed_job], Qu[https://github.com/bkeepers/qu] and so on. [http://guides.rubyonrails.org/4_2_release_notes.html] Overall, Active Job is a interface which you can work with common queues. | ||
__TOC__ | __TOC__ | ||
Revision as of 14:25, 31 January 2016
Introduction
Active Job is a framework help developers writing codes and run them on the background automatically under different scenarios. Jobs can vary from schedule newsletter, follow-up emails to database housekeeping. It’s a interface that adapts different queueing backends like Backburner[1], Delayed Job[2], Qu[3] and so on. [4] Overall, Active Job is a interface which you can work with common queues.