Job priorities and queues in Ruby on Rails - Mini Project: Build & Apply

Job priorities and queues

📖 Scenario: You are building a simple background job system in a Rails app. Jobs have different priorities and are placed in different queues based on their priority.This helps the app process urgent tasks faster and less urgent tasks later.

🎯 Goal: Create a basic job class with priority levels and assign jobs to queues accordingly.Learn how to set up job priorities and queues in Rails Active Job.

📋 What You'll Learn

Create a job class with a priority attribute

Define queues for high, medium, and low priority jobs

Assign jobs to the correct queue based on priority

Enqueue jobs with different priorities

💡 Why This Matters

🌍 Real World

Many web apps use background jobs to handle tasks like sending emails or processing data. Prioritizing jobs helps important tasks run faster.

💼 Career

Understanding job priorities and queues is essential for backend developers working with Rails and background processing frameworks like Sidekiq or Delayed Job.

1

Create a job class with a priority attribute

Create a Rails job class called PriorityJob that inherits from ApplicationJob. Add an attr_accessor for priority.

Ruby on Rails

class PriorityJob < ApplicationJob
  # Your code here
end

Hint

Use attr_accessor :priority inside the job class to add a priority attribute.

2

Define queues for high, medium, and low priority jobs

Inside the PriorityJob class, define three queues named high_priority, medium_priority, and low_priority using queue_as method. Use a method queue_name that returns the queue name based on the priority value: 'high' maps to :high_priority, 'medium' to :medium_priority, and 'low' to :low_priority. Then set queue_as :queue_name dynamically.

Ruby on Rails

class PriorityJob < ApplicationJob
  attr_accessor :priority

  # Your code here to define queues and queue_name method
end

Hint

Use a case statement inside queue_name to return the correct queue symbol.

Use queue_as :queue_name to set the queue dynamically.

3

Assign jobs to the correct queue based on priority

Add an initialize method to PriorityJob that accepts a priority argument and sets the priority attribute. This will ensure each job instance knows its priority and queue.

Ruby on Rails

class PriorityJob < ApplicationJob
  attr_accessor :priority

  def initialize(priority)
    # Your code here to set priority
  end

  def queue_name
    case priority
    when 'high' then :high_priority
    when 'medium' then :medium_priority
    else :low_priority
    end
  end

  queue_as :queue_name
end

Hint

Define initialize(priority) and set @priority = priority.

4

Enqueue jobs with different priorities

In your Rails app, enqueue three PriorityJob jobs with priorities 'high', 'medium', and 'low' using PriorityJob.new(priority).enqueue or perform_later if preferred. This will place each job in the correct queue.

Ruby on Rails

class PriorityJob < ApplicationJob
  attr_accessor :priority

  def initialize(priority)
    @priority = priority
  end

  def queue_name
    case priority
    when 'high' then :high_priority
    when 'medium' then :medium_priority
    else :low_priority
    end
  end

  queue_as :queue_name
end

# Your code here to enqueue jobs with different priorities

Hint

Call PriorityJob.perform_later('high') and similarly for 'medium' and 'low'.

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