Job priorities and queues in Ruby on Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a job queue in Rails Active Job?

A job queue is a list where background jobs wait to be processed. Rails Active Job lets you put tasks like sending emails or processing images into queues to run later without blocking the main app.

intermediate

How do you assign a priority to a job in Rails?

You assign a priority by choosing or creating different queues with names that imply priority, like 'high_priority' or 'low_priority'. Jobs in higher priority queues get processed before others.

intermediate

What is the role of a queue adapter in Rails Active Job?

A queue adapter connects Rails Active Job to the backend system that actually runs the jobs, like Sidekiq or Resque. It manages how jobs are pushed to and pulled from queues.

beginner

How can you specify which queue a job should use in Rails?

Inside your job class, you use the `queue_as` method to name the queue. For example, `queue_as :mailers` sends the job to the 'mailers' queue.

intermediate

Why use multiple queues with different priorities in a Rails app?

Using multiple queues lets you control which jobs run first. Important tasks like sending notifications can go to a high-priority queue, so they run faster, while less urgent jobs wait in lower-priority queues.

In Rails Active Job, how do you set a job to run in a specific queue?

A Use `queue_as :queue_name` inside the job class

B Call `set_queue('queue_name')` in the controller

C Rename the job file to the queue name

D Set the queue name in the database

You specify the queue inside the job class using `queue_as :queue_name`.

What does a queue adapter do in Rails Active Job?

A Automatically retries failed jobs without configuration

B Connects Active Job to the backend system that runs jobs

C Schedules jobs to run only during business hours

D Generates job classes automatically

The queue adapter links Active Job to the system like Sidekiq that processes jobs.

Why might you use multiple queues with different priorities?

A To make jobs run faster by splitting them randomly

B To reduce the number of jobs in the system

C To control the order jobs are processed based on importance

D To avoid using background jobs

Multiple queues let you prioritize important jobs to run before less important ones.

Which of these is NOT a common queue adapter in Rails?

A Sidekiq

B Resque

C Delayed Job

D Webpacker

Webpacker is for managing JavaScript assets, not job queues.

What happens if you don't specify a queue for a job in Rails Active Job?

A The job goes to the default queue

B Rails throws an error

C The job is discarded

D The job runs immediately without queuing

Jobs without a specified queue go to the default queue.

Explain how job priorities and queues work in Rails Active Job and why they are useful.

Think about how you organize tasks by importance in real life.

Describe the role of a queue adapter in Rails and name some common adapters.

Adapters connect Rails to the system that runs jobs.

Practice

1. What is the main purpose of setting different job priorities in Rails Active Job?

easy

A. To run more important tasks before less important ones

B. To make jobs run slower

C. To delete jobs automatically

D. To run all jobs at the same time

Solution

1. Step 1: Understand job priorities concept

   Job priorities help decide which jobs run first based on importance.

2. Step 2: Identify the purpose in Rails

   Rails uses priorities to run important jobs before less important ones.

3. Final Answer:

   To run more important tasks before less important ones -> Option A

4. Quick Check:

   Job priorities = run important jobs first [OK]

Hint: Priorities mean important jobs run before others [OK]

Common Mistakes:

• Thinking priorities slow down jobs
• Assuming priorities delete jobs
• Believing all jobs run simultaneously

2. Which syntax correctly sets a queue name for a job class in Rails?

easy

A. queue_as :default

B. queue = :default

C. set_queue :default

D. queue_name = 'default'

Solution

1. Step 1: Recall Rails Active Job syntax

   Rails uses queue_as to set the queue name inside job classes.

2. Step 2: Match correct syntax

   queue_as :default is the correct way to assign the queue.

3. Final Answer:

   queue_as :default -> Option A

4. Quick Check:

   Use queue_as to set queue [OK]

Hint: Use queue_as :name inside job class [OK]

Common Mistakes:

• Using assignment (=) instead of queue_as
• Trying to set queue with unknown methods
• Using string instead of symbol incorrectly

3. Given this job class:

class EmailJob < ApplicationJob
  queue_as :mailers
  def perform(user_id)
    # send email
  end
end

Which queue will this job be added to when enqueued?

medium

A. jobs

B. default

C. emails

D. mailers

Solution

1. Step 1: Check the queue_as setting in the job class

   The job class sets queue_as :mailers, so it uses the 'mailers' queue.

2. Step 2: Understand enqueue behavior

   When enqueued, the job goes to the queue named 'mailers'.

3. Final Answer:

   mailers -> Option D

4. Quick Check:

   queue_as :mailers means queue is 'mailers' [OK]

Hint: queue_as sets the queue name exactly [OK]

Common Mistakes:

• Assuming default queue if queue_as is set
• Confusing queue name with job class name
• Picking similar sounding queue names

4. Identify the error in this job class:

class CleanupJob < ApplicationJob
  queue_as = :low_priority
  def perform
    # cleanup code
  end
end

medium

A. Job class must inherit from ActiveJob::Base

B. perform method must have an argument

C. queue_as should be called as a method, not assigned

D. queue_as must be a string, not a symbol

Solution

1. Step 1: Check how queue_as is set

   queue_as is a method call, not an assignment. Using '=' causes syntax error.

2. Step 2: Correct syntax for queue_as

   It should be queue_as :low_priority without '='.

3. Final Answer:

   queue_as should be called as a method, not assigned -> Option C

4. Quick Check:

   queue_as is a method call, not variable assignment [OK]

Hint: Use queue_as :name, not queue_as = :name [OK]

Common Mistakes:

• Using '=' with queue_as
• Forgetting to inherit from ApplicationJob
• Thinking perform must have arguments always

5. You want to run urgent jobs before normal jobs in Rails. You have two job classes:

class UrgentJob < ApplicationJob
  queue_as :urgent
  def perform
    # urgent task
  end
end

class NormalJob < ApplicationJob
  queue_as :normal
  def perform
    # normal task
  end
end

How can you ensure urgent jobs run before normal jobs when using Sidekiq?

hard

A. Rename UrgentJob to NormalJob

B. Configure Sidekiq to process the 'urgent' queue before the 'normal' queue

C. Set both jobs to the same queue

D. Run urgent jobs manually without Sidekiq

Solution

1. Step 1: Understand queue priority in Sidekiq

   Sidekiq processes queues in the order they are listed in its configuration.

2. Step 2: Set Sidekiq to prioritize 'urgent' queue

   Configure Sidekiq to check the 'urgent' queue before 'normal' to run urgent jobs first.

3. Final Answer:

   Configure Sidekiq to process the 'urgent' queue before the 'normal' queue -> Option B

4. Quick Check:

   Sidekiq queue order controls job priority [OK]

Hint: Set queue order in Sidekiq config for priority [OK]

Common Mistakes:

• Assuming queue_as alone controls priority
• Renaming job classes does not affect queue order
• Running urgent jobs manually is inefficient