Rails Jobs

Use for background job design and review. Patterns from Campfire (Resque, 4 thin jobs) and Fizzy (Solid Queue, multi-queue).

Defaults

• Keep jobs shallow; the job body is one line calling a model method: def perform(card) = card.notify_recipients.
• Make jobs idempotent and safe to retry (e.g. rescue RecordNotUnique in the domain op).
• Fail loudly on real errors; avoid silent rescue patterns.
• Set ActiveJob::Base.enqueue_after_transaction_commit = true in app defaults, fixes job-before-data races at the root.
• Prefer Solid Queue (database-backed) over Redis-backed queues for new apps; co-locate with Puma (SOLID_QUEUE_IN_PUMA) in small deployments.

Naming Convention

• _later enqueues, plain name does the work, _now when you need an explicit synchronous twin:

def notify_recipients          # the work, public API the job calls
def notify_recipients_later   # enqueues NotifyRecipientsJob (often private, called from callbacks)

• Capture enqueue-time context as keyword args (Mention::CreateJob.perform_later(self, mentioner: Current.user)), don't rely on Current at perform time.
• In multi-tenant apps, serialize tenant context into every job: prepend an ApplicationJob extension that captures Current.account at enqueue (as a GlobalID) and wraps perform_now in Current.with_account.

Good Patterns