1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Ruby on Rails
Find a file
David Heinemeier Hansson c69dda4988 Add justification
2014-05-19 13:13:30 +02:00
lib Move to instance method and document usage 2014-05-19 12:46:27 +02:00
test Move to instance method and document usage 2014-05-19 12:46:27 +02:00
activejob.gemspec Move activemodel-globalid dependency to gemspec 2014-05-19 12:39:14 +02:00
CHANGELOG.md Skeleton gem 2014-05-18 11:44:28 +02:00
Gemfile Move activemodel-globalid dependency to gemspec 2014-05-19 12:39:14 +02:00
Gemfile.lock Move activemodel-globalid dependency to gemspec 2014-05-19 12:39:14 +02:00
MIT-LICENSE Skeleton gem 2014-05-18 11:44:28 +02:00
Rakefile Implemented delayed job 2014-05-19 11:41:04 +03:00
README.md Add justification 2014-05-19 13:13:30 +02:00

Active Job -- Make work happen later

Active Job is a framework for declaring jobs and making them run on a variety of queueing backends. These jobs can be everything from regularly scheduled clean-ups, billing charges, or mailings. Anything that can be chopped up into small units of work and run in parallel, really.

It also serves as the backend for ActionMailer's #deliver_later functionality that makes it easy to turn any mailing into a job for running later. That's one of the most common jobs in a modern web application: Sending emails outside of the request-response cycle, so the user doesn't have to wait on it.

The main point is to ensure that all Rails apps will have a job infrastructure in place, even if it's in the form of an "immediate runner". We can then have framework features and other gems build on top of that, without having to worry about API differences between Delayed Job and Resque. Picking your queuing backend becomes more of an operational concern, then. And you'll be able to switch between them without having to rewrite your jobs.

Usage

Declare a job like so:

class MyJob < ActiveJob::Base
  def perform(record)
    record.do_work
  end
end

Enqueue a job like so:

MyJob.enqueue record

That's it!

GlobalID support

Active Job supports GlobalID serialization for parameters. This makes it possible to pass live Active Record objects to your job instead of class/id pairs, which you then have to manually deserialize. Before, jobs would look like this:

class TrashableCleanupJob
  def perfom(trashable_class, trashable_id, depth)
    trashable = trashable_class.constantize.find(trashable_id)
    trashable.cleanup(depth)
  end
end

Now you can simply do:

class TrashableCleanupJob
  def perfom(trashable, depth)
    trashable.cleanup(depth)
  end
end

This works with any class that mixes in ActiveModel::GlobalIdentification, which by default has been mixed into Active Record classes.

Supported queueing systems

We currently have adapters for:

  • Resque 1.x
  • Sidekiq
  • Sucker Punch
  • Delayed Job

We would like to have adapters for:

  • beanstalkd
  • rabbitmq

Under development as a gem, targeted for Rails inclusion

Active Job is currently being developed in a separate repository until it's ready to be merged in with Rails. The current plan is to have Active Job be part of the Rails 4.2 release, but plans may change depending on when this framework stabilizes and feels ready.

License

Active Job is released under the MIT license: