background-jobs

Background jobs in Rust can run outside the HTTP request cycle by enqueuing work from server functions to durable workers. This pattern uses apalis with a Postgres backend to queue and process long-running jobs like emails, reports, and webhooks reliably.

Scheduling cron jobs with apalis involves using apalis-cron alongside Postgres storage to manage recurring work. This setup supports durable workers that execute scheduled tasks and standard background jobs within the same Rust application.

The background worker pattern handles task failures using built-in retry logic and a dead-letter queue. When a queued job fails repeatedly, it routes to the dead-letter workflow, preventing data loss during long-running work processing.

You can enqueue background jobs directly from server functions in a Leptos application. The implementation enforces enqueue-from-server-fn semantics at startup, ensuring that tasks are safely queued to the Postgres storage backend.

You need a Postgres database to provide durable storage for background jobs using apalis. The Postgres backend acts as the storage layer for queuing, retrying, and managing the dead-letter queue for long-running work.