ActiveJob for queue adapter abstraction

12030 views

                  class ProcessUploadJob < ApplicationJob
  queue_as :default

  retry_on StandardError, wait: :exponentially_longer, attempts: 5
  discard_on ActiveJob::DeserializationError

  def perform(upload_id)
    upload = Upload.find(upload_id)

    # Process the upload
    processor = UploadProcessor.new(upload)
    processor.process!

    upload.update!(status: 'completed', processed_at: Time.current)
  rescue StandardError => e
    upload.update!(status: 'failed', error_message: e.message)
    raise e
  end
end

                  module MyApp
  class Application < Rails::Application
    config.load_defaults 6.1

    # Set ActiveJob adapter
    config.active_job.queue_adapter = :sidekiq

    # Configure queue priority
    config.active_job.queue_name_prefix = Rails.env
  end
end

ActiveJob provides a unified interface across different queue backends (Sidekiq, Resque, Delayed Job), making it easier to switch adapters or test jobs. I define jobs by inheriting from ApplicationJob and implementing perform. ActiveJob handles serialization, queue routing, and retry logic automatically. The abstraction layer means tests can use the :inline or :test adapter while production uses Sidekiq. I configure queues with priority in application.rb and route jobs to specific queues based on their characteristics. For simple background work, ActiveJob is sufficient. For advanced features like batches, rate limiting, or complex scheduling, I drop down to Sidekiq-specific APIs.

Alex Kumar

More from Alex Kumar

ActiveJob for queue adapter abstraction

0 Comments

More from Alex Kumar