./devel/ruby-activejob72, Job classes that can be run by a variety of queueing backends

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 7.2.2.1, Package name: ruby32-activejob72-7.2.2.1, Maintainer: pkgsrc-users

Active Job - Make work happen later

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

It also serves as the backend for Action Mailer'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 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.

This is for Ruby on Rails 7.2.

Master sites:

Filesize: 35.5 KB

Version history: (Expand)

CVS history: (Expand)


   2024-12-13 17:42:42 by Takahiro Kambe | Files touched by this commit (4) 
Log message:
devel/ruby-activejob72: add package version 7.2.2.1

Active Job - Make work happen later

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

It also serves as the backend for Action Mailer'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 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.