Vanilla Rails Jobs

Jobs are thin wrappers (3-5 lines). ALL business logic lives in models.

The Pattern

# Model concern - WHERE THE LOGIC LIVES
module Card::ClosureNotifications
  extend ActiveSupport::Concern

  included do
    after_update :notify_watchers_later, if: :just_closed?
  end

  def notify_watchers_later
    Card::ClosureNotificationJob.perform_later(self)
  end

  def notify_watchers_now
    watchers.each do |watcher|
      CardMailer.closure_notification(watcher, self).deliver_now
      Notification.create!(user: watcher, card: self, action: 'closed')
    end
  end
end

# Job - ONLY delegates (3 lines)
class Card::ClosureNotificationJob < ApplicationJob
  def perform(card)
    card.notify_watchers_now
  end
end

Flow: Callback → _later → enqueue job → job calls _now → logic executes

Why Thin Jobs

• Test _now synchronously — no job infrastructure needed
• Reusable — call _now in console, tests, anywhere
• Debuggable — stack traces point to model, not job framework

Edge Cases

Multi-model — primary model orchestrates:

class User::DigestJob < ApplicationJob
  def perform(user); user.send_digest_now; end
end

Utility/cleanup — use class methods:

class Session::CleanupJob < ApplicationJob
  def perform; Session.cleanup_expired_now; end
end

Error handling — ActiveJob retries + model errors:

class Card::SyncJob < ApplicationJob
  retry_on ExternalAPI::Error, wait: 5.minutes
  def perform(card); card.sync_to_external_system_now; end
end

Red Flags

Quick Check

• Job is 3-5 lines, calls one model method
• Receives model instance (not ID)
• No queries, conditionals, or loops in job
• Model has _later method (enqueues)
• Model has _now method (logic)