Active Job framework in Ruby on Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the Active Job framework in Rails?

Active Job provides a simple way to declare jobs and run them on various queueing backends. It helps you run tasks in the background, like sending emails or processing data, without blocking the main app.

beginner

How do you create a new job using Active Job?

You create a new job by running rails generate job JobName. This creates a job file where you define the perform method with the task you want to run in the background.

beginner

What method do you call to run a job asynchronously in Active Job?

You call <code>perform_later</code> on the job class to enqueue the job to run in the background. For example, <code>MyJob.perform_later(args)</code>.

intermediate

Name two queue adapters supported by Active Job.

Active Job supports many adapters like Sidekiq, Resque, Delayed Job, and the default Async adapter.

intermediate

Why is Active Job useful when switching queue backends?

Active Job provides a unified interface for jobs. This means you can switch queue backends (like from Sidekiq to Resque) without changing your job code, making your app flexible and easier to maintain.

Which method enqueues a job to run later in Active Job?

A run_async

B perform_now

C perform_later

D enqueue_job

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

What file is generated when you run rails generate job JobName?

A A migration file

B A model file

C A controller file

D A job file with a perform method

Generating a job creates a job file where you define the perform method for background tasks.

Which of these is NOT a queue adapter supported by Active Job?

A Puma

B Resque

C Sidekiq

D Delayed Job

Puma is a web server, not a queue adapter. Sidekiq, Resque, and Delayed Job are queue adapters.

What is the default queue adapter in Active Job if none is specified?

A Async

B Sidekiq

C Resque

D Delayed Job

The default adapter is Async, which runs jobs in separate threads within the Rails process.

Why use Active Job instead of directly using a queue adapter?

A It runs jobs faster

B It makes switching adapters easier

C It replaces the need for background jobs

D It automatically scales servers

Active Job abstracts queue adapters, so you can switch them without changing your job code.

Explain how Active Job helps manage background tasks in a Rails app.

Think about how you would send emails or process data without slowing down the app.

Describe the steps to create and run a background job using Active Job.

Start from creating the job file to making it run in the background.

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