Active Job framework in Ruby on Rails - Step-by-Step Execution

Concept Flow - Active Job framework

Define Job Class

↓

Enqueue Job

↓

Job Added to Queue

↓

Job Worker Picks Job

↓

Perform Job's perform Method

↓

Job Completes

↓

Optional Callbacks Triggered

Active Job lets you define background tasks, enqueue them, and workers run them asynchronously.

Execution Sample

Ruby on Rails

class MyJob < ApplicationJob
  queue_as :default

  def perform(name)
    puts "Hello, #{name}!"
  end
end

MyJob.perform_later('Alice')

Defines a job that prints a greeting and enqueues it to run later.

Execution Table

Step	Action	Details	Result
1	Define Job Class	MyJob inherits ApplicationJob with perform(name)	Job class ready
2	Call perform_later('Alice')	Enqueue job with argument 'Alice'	Job added to default queue
3	Worker picks job	Background worker fetches job from queue	Job instance created with name='Alice'
4	Call perform method	Run perform('Alice')	Outputs: Hello, Alice!
5	Job finishes	Job completes successfully	Job removed from queue
6	Optional callbacks	After perform callbacks run if defined	Callbacks executed if any

💡 Job completes and is removed from queue after perform method runs

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
name	nil	nil	'Alice'	'Alice'	'Alice'
job_instance	nil	nil	MyJob instance with name='Alice'	Same instance	Destroyed after completion
queue	empty	contains MyJob with 'Alice'	contains MyJob with 'Alice'	empty	empty

Key Moments - 3 Insights

Why doesn't perform_later run the job immediately?

perform_later only adds the job to the queue (see Step 2). The job runs later when a worker picks it (Step 3).

What happens if the job fails during perform?

If perform raises an error, the job may be retried or moved to a dead queue depending on configuration, not shown here.

How does the job get the argument 'Alice'?

The argument 'Alice' is passed when enqueuing (Step 2) and stored in the job instance for perform (Step 3).

Visual Quiz - 3 Questions

Look at the execution table, what is the output at Step 4?

A "Hello, Alice!"

B Job added to queue

C Job instance created

D Job removed from queue

💡 Hint

Check the 'Result' column at Step 4 in the execution_table

At which step does the job get removed from the queue?

A Step 2

B Step 5

C Step 3

D Step 6

💡 Hint

Look for when the queue becomes empty in variable_tracker and the 'Job removed from queue' note in execution_table

If you call perform_now instead of perform_later, what changes in the execution flow?

A Job is enqueued twice

B Job is added to queue but never performed

C Job runs immediately, skipping queue and worker steps

D Job runs only after callbacks

💡 Hint

Consider how perform_now differs from perform_later in Active Job behavior

Concept Snapshot

Active Job lets you run background tasks.
Define a job class with perform method.
Use perform_later to enqueue, perform_now to run immediately.
Jobs run asynchronously via workers.
Arguments pass through enqueue to perform.
Callbacks run after job completion.

Full Transcript

Active Job framework in Rails helps run tasks in the background. You define a job class inheriting ApplicationJob with a perform method. Calling perform_later enqueues the job with arguments. A background worker picks the job from the queue and runs perform with those arguments. After perform finishes, the job is removed from the queue and optional callbacks run. This lets your app do work later without blocking user requests. perform_now runs the job immediately without queueing. Variables like job arguments and queue state change step-by-step as the job moves from enqueue to execution to completion.

Practice

1. What is the main purpose of Active Job in Rails?

easy

A. To create database tables automatically

B. To run tasks in the background without blocking the main app

C. To handle user authentication

D. To style HTML pages with CSS

Solution

1. Step 1: Understand Active Job's role

   Active Job is designed to run tasks asynchronously, meaning it runs jobs in the background.

2. Step 2: Compare options with Active Job's purpose

   Database table creation, user authentication, and page styling are not Active Job's focus.

3. Final Answer:

   To run tasks in the background without blocking the main app -> Option B

4. Quick Check:

   Background tasks = A [OK]

Hint: Active Job runs tasks behind the scenes, not user-facing features [OK]

Common Mistakes:

• Confusing Active Job with database migrations
• Thinking Active Job handles user login
• Assuming Active Job styles pages

2. Which of the following is the correct way to enqueue a job to run later in Active Job?

easy

A. MyJob.perform_later(args)

B. MyJob.perform_now(args)

C. MyJob.enqueue(args)

D. MyJob.run_async(args)

Solution

1. Step 1: Recall Active Job enqueue methods

   Active Job uses perform_later to enqueue jobs to run asynchronously.

2. Step 2: Check each option's validity

   perform_now runs immediately, enqueue and run_async are not valid Active Job methods.

3. Final Answer:

   MyJob.perform_later(args) -> Option A

4. Quick Check:

   Use perform_later to enqueue jobs [OK]

Hint: Use perform_later to run jobs later, not perform_now [OK]

Common Mistakes:

• Using perform_now instead of perform_later
• Trying to call enqueue or run_async which don't exist
• Confusing method names

3. Given this job class:

class GreetingJob < ApplicationJob
  def perform(name)
    puts "Hello, #{name}!"
  end
end

GreetingJob.perform_later('Alice')

What will happen when this code runs?

medium

A. Prints 'Hello, Alice!' immediately

B. Raises a syntax error

C. Prints 'Hello, Alice!' in the background later

D. Does nothing because perform_later is invalid

Solution

1. Step 1: Understand perform_later behavior

   The perform_later method enqueues the job to run asynchronously in the background.

2. Step 2: Analyze the output timing

   The puts inside perform runs when the job executes later, not immediately.

3. Final Answer:

   Prints 'Hello, Alice!' in the background later -> Option C

4. Quick Check:

   perform_later runs job later, not now [OK]

Hint: perform_later delays execution; output appears later [OK]

Common Mistakes:

• Thinking perform_later runs immediately
• Assuming perform_later is invalid
• Confusing perform_later with perform_now

4. Identify the error in this Active Job class:

class EmailJob < ApplicationJob
  def perform
    UserMailer.welcome_email.deliver_now
  end
end

medium

A. perform method should be private

B. deliver_now is not allowed inside jobs

C. Job class must not inherit ApplicationJob

D. Missing argument in perform method

Solution

1. Step 1: Check perform method signature

   The mailer method likely needs a user argument, but perform has no parameters to receive it.

2. Step 2: Understand job argument passing

   Jobs should accept arguments in perform to pass data like user info; missing argument causes errors.

3. Final Answer:

   Missing argument in perform method -> Option D

4. Quick Check:

   perform needs parameters for job data [OK]

Hint: perform method must accept needed arguments [OK]

Common Mistakes:

• Ignoring missing parameters in perform
• Thinking deliver_now is forbidden in jobs
• Believing ApplicationJob inheritance is wrong

5. You want to send a welcome email to a user after they sign up, but only if their email is verified. Which is the best way to use Active Job for this?

hard

A. Call WelcomeEmailJob.perform_later(user) only after checking user.email_verified?

B. Call WelcomeEmailJob.perform_later(user) unconditionally and check verification inside the job

C. Send the email directly in the controller without using Active Job

D. Use perform_now to send the email immediately regardless of verification

Solution

1. Step 1: Understand conditional job enqueueing

   It's best to enqueue the job only if the user is verified to avoid unnecessary background work.

2. Step 2: Compare options for efficiency and correctness

   Sending synchronously in the controller blocks the web request; enqueuing unconditionally wastes resources by processing jobs that may do nothing; using perform_now ignores verification and blocks the request.

3. Final Answer:

   Call WelcomeEmailJob.perform_later(user) only after checking user.email_verified? -> Option A

4. Quick Check:

   Enqueue jobs conditionally for efficiency [OK]

Hint: Check conditions before enqueueing jobs to save resources [OK]

Common Mistakes:

• Enqueueing jobs without checking conditions
• Sending emails synchronously blocking app
• Ignoring user verification status