Job creation and queuing in Ruby on Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of Active Job in Rails?

Active Job is a framework for declaring jobs and making them run on a variety of queueing backends. It helps you run tasks in the background, like sending emails or processing files, so your app stays fast and responsive.

beginner

How do you create a new job in Rails 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 does the perform_later method do in Rails jobs?

The perform_later method tells Rails to put the job into the queue to run later in the background. It does not run the job immediately but schedules it to run asynchronously.

intermediate

Name two popular queue adapters supported by Rails Active Job.

Two popular queue adapters are Sidekiq and Delayed Job. Sidekiq uses Redis and is fast and efficient. Delayed Job uses the database to store jobs and is easy to set up.

beginner

Why is it important to use background jobs for tasks like sending emails or processing images?

Background jobs let your app handle slow tasks without making users wait. For example, sending an email can take time, so doing it in the background keeps the app fast and smooth for users.

Which method schedules a job to run asynchronously in Rails Active Job?

A perform_later

B perform_now

C run_job

D enqueue_job

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

What command creates a new job file in Rails?

A rails create job JobName

B rails new job JobName

C rails generate job JobName

D rails job new JobName

The correct command is rails generate job JobName to create a new job.

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

A Puma

B Sidekiq

C Resque

D Delayed Job

Puma is a web server, not a queue adapter.

Why should long-running tasks be moved to background jobs?

A To avoid using the database

B To keep the app responsive and fast for users

C To make the app slower

D To run tasks only during the day

Background jobs keep the app responsive by running slow tasks separately.

What does the perform method inside a job class do?

A Schedules the job to run later

B Starts the Rails server

C Creates a new job file

D Defines the task to run when the job executes

The perform method contains the code that runs when the job is processed.

Explain how to create and run a background job in Rails using Active Job.

Think about the steps from creating the job file to scheduling it.

Why is queuing jobs important in web applications? Give examples of tasks suited for background jobs.

Consider what happens if slow tasks run during user requests.

Practice

1. What is the main purpose of creating a job in Rails using ApplicationJob?

easy

A. To run tasks in the background without blocking the main app flow

B. To create database tables automatically

C. To handle user authentication

D. To style the user interface

Solution

1. Step 1: Understand the role of jobs in Rails

   Jobs are designed to run tasks asynchronously, so they don't slow down the main app.

2. Step 2: Identify the correct purpose

   Running tasks in the background matches the job's purpose, unlike database creation or UI styling.

3. Final Answer:

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

4. Quick Check:

   Jobs = background tasks [OK]

Hint: Jobs run tasks later to keep app fast [OK]

Common Mistakes:

• Thinking jobs create database tables
• Confusing jobs with UI styling
• Assuming jobs handle user login

2. Which of the following is the correct way to enqueue a job named SendEmailJob to run later?

easy

A. SendEmailJob.perform_later

B. SendEmailJob.run_later

C. SendEmailJob.enqueue

D. SendEmailJob.perform_now

Solution

1. Step 1: Recall the method to queue jobs in Rails

   The method perform_later adds the job to the queue for later execution.

2. Step 2: Compare options

   perform_now runs immediately, enqueue and run_later are not valid Rails job methods.

3. Final Answer:

   SendEmailJob.perform_later -> Option A

4. Quick Check:

   Use perform_later to queue jobs [OK]

Hint: Use perform_later to queue jobs [OK]

Common Mistakes:

• Using perform_now instead of perform_later
• Using non-existent methods like enqueue or run_later
• Confusing immediate execution with queuing

3. Given this job definition:

class CleanupJob < ApplicationJob
  def perform
    puts 'Cleaning up!'
  end
end

What will happen when you call CleanupJob.perform_later?

medium

A. Prints 'Cleaning up!' immediately

B. Adds the job to the queue and prints 'Cleaning up!' later

C. Raises an error because perform_later is undefined

D. Does nothing because perform is empty

Solution

1. Step 1: Understand perform_later behavior

   Calling perform_later queues the job to run asynchronously later, not immediately.

2. Step 2: Check the perform method

   The perform method prints 'Cleaning up!' when the job runs, so this will happen later after queuing.

3. Final Answer:

   Adds the job to the queue and prints 'Cleaning up!' later -> Option B

4. Quick Check:

   perform_later queues job, runs perform later [OK]

Hint: perform_later queues job, runs perform method later [OK]

Common Mistakes:

• Thinking perform_later runs perform immediately
• Assuming perform_later is undefined
• Believing perform method is empty and does nothing

4. Identify the error in this job code:

class NotifyUserJob < ApplicationJob
  def perform(user_id)
    User.find(user_id).notify
  end
end

NotifyUserJob.perform_later

medium

A. Cannot inherit from ApplicationJob

B. Wrong method name; should be perform_now

C. User model does not exist

D. Missing argument when calling perform_later

Solution

1. Step 1: Check perform method parameters

   The perform method requires one argument: user_id.

2. Step 2: Check perform_later call

   Calling perform_later without arguments causes an error because user_id is missing.

3. Final Answer:

   Missing argument when calling perform_later -> Option D

4. Quick Check:

   perform_later needs all perform arguments [OK]

Hint: Always pass perform arguments to perform_later [OK]

Common Mistakes:

• Calling perform_later without required arguments
• Confusing perform_later with perform_now
• Assuming inheritance from ApplicationJob is invalid

5. You want to create a job that sends a welcome email only if the user has verified their email. Which is the best way to implement this in perform?

hard

A. Raise an error if user is not verified inside perform

B. Send email unconditionally in perform and handle verification elsewhere

C. Check user.verified? inside perform and send email only if true

D. Call perform_now instead of perform_later

Solution

1. Step 1: Understand conditional logic in jobs

   Jobs can include logic to decide whether to perform actions, like checking if user is verified.

2. Step 2: Evaluate options

   Check user.verified? inside perform and send email only if true correctly checks verification inside perform before sending email, ensuring only verified users get emails.

3. Final Answer:

   Check user.verified? inside perform and send email only if true -> Option C

4. Quick Check:

   Use condition inside perform for selective job actions [OK]

Hint: Put conditions inside perform to control job actions [OK]

Common Mistakes:

• Sending emails without checking verification
• Raising errors unnecessarily in perform
• Confusing perform_now with perform_later