34 releases

new 0.6.0-rc.4 Jul 19, 2024
0.6.0-alpha.0 Jun 30, 2024
0.5.1 Mar 13, 2024
0.4.7 Nov 18, 2023
0.2.0 May 14, 2021

#279 in Database interfaces

Download history 3104/week @ 2024-03-29 4480/week @ 2024-04-05 4373/week @ 2024-04-12 6269/week @ 2024-04-19 5538/week @ 2024-04-26 5425/week @ 2024-05-03 7462/week @ 2024-05-10 4998/week @ 2024-05-17 6495/week @ 2024-05-24 3847/week @ 2024-05-31 5453/week @ 2024-06-07 5299/week @ 2024-06-14 6477/week @ 2024-06-21 3617/week @ 2024-06-28 5199/week @ 2024-07-05 3645/week @ 2024-07-12

19,928 downloads per month
Used in 5 crates (via apalis)

MIT license



Simple, extensible multithreaded background job and messages processing library for Rust


  • Simple and predictable job handling model.
  • Jobs handlers with a macro free API.
  • Take full advantage of the tower ecosystem of middleware, services, and utilities.
  • Runtime agnostic - Use tokio, smol etc.
  • Optional Web interface to help you manage your jobs.

apalis job processing is powered by tower::Service which means you have access to the tower middleware.

apalis has support for:

Source Crate Example
Cron Jobs
From Scratch

Getting Started

To get started, just add to Cargo.toml

apalis = { version = "0.6" }
apalis-redis = { version = "0.6" }
# apalis-sql = { version = "0.6", features = ["postgres"] } # or mysql, sqlite


use apalis::prelude::*;
use apalis_redis::{RedisStorage, Config};
use serde::{Deserialize, Serialize};

#[derive(Debug, Deserialize, Serialize)]
struct Email {
    to: String,

/// A function that will be converted into a service.
async fn send_email(job: Email, data: Data<usize>) -> Result<(), Error> {
  /// execute job

async fn main() -> {
    std::env::set_var("RUST_LOG", "debug");
    let redis_url = std::env::var("REDIS_URL").expect("Missing env variable REDIS_URL");
    let conn = apalis_redis::connect(redis_url).await.expect("Could not connect");
    let storage = RedisStorage::new(conn);
        .register_with_count(2, {


//This can be in another part of the program or another application eg a http server
async fn produce_route_jobs(storage: &RedisStorage<Email>) -> Result<()> {
    let mut storage = storage.clone();
        .push(Email {
            to: "test@example.com".to_string(),

Feature flags

  • tracing (enabled by default) — Support Tracing 👀
  • sentry — Support for Sentry exception and performance monitoring
  • prometheus — Support Prometheus metrics
  • retry — Support direct retrying jobs
  • timeout — Support timeouts on jobs
  • limit — 💪 Limit the amount of jobs
  • filter — Support filtering jobs based on a predicate
  • catch-panic - Catch panics that occur during execution

Storage Comparison

Since we provide a few storage solutions, here is a table comparing them:

Feature Redis Sqlite Postgres Sled Mysql Mongo Cron
Scheduled jobs x x
Retry jobs x x
Persistence x x BYO
Rerun Dead jobs x x x

How apalis works

Here is a basic example of how the core parts integrate

    participant App
    participant Worker
    participant Backend

    App->>+Backend: Add job to queue
    Backend-->>+Worker: Job data
    Worker->>+Backend: Update job status to 'Running'
    Worker->>+App: Started job
    loop job execution
        Worker-->>-App: Report job progress
    Worker->>+Backend: Update job status to 'completed'

External examples

Projects using apalis

  • Ryot: A self hosted platform for tracking various facets of your life - media, fitness etc.
  • Summarizer: Podcast summarizer
  • Universal Inbox: Universal Inbox is a solution that centralizes all your notifications and tasks in one place to create a unique inbox.


Web UI

If you are running apalis Board, you can easily manage your jobs. See a working rest API example here

Thanks to

  • tower - Tower is a library of modular and reusable components for building robust networking clients and servers.
  • redis-rs - Redis library for rust
  • sqlx - The Rust SQL Toolkit


v 0.5

  • Refactor the crates structure
  • Mocking utilities
  • Support for SurrealDB and Mongo
  • Lock free for Postgres
  • Add more utility layers
  • Use extractors in job fn structure
  • Polish up documentation
  • Improve and standardize apalis Board
  • Benchmarks

v 0.4

  • Move from actor based to layer based processing
  • Graceful Shutdown
  • Allow other types of executors apart from Tokio
  • Mock/Test Worker
  • Improve monitoring
  • Add job progress via layer
  • Add more sources

v 0.3

  • Standardize API (Storage, Worker, Data, Middleware, Context )
  • Introduce SQL
  • Implement layers for Sentry and Tracing.
  • Improve documentation
  • Organized modules and features.
  • Basic Web API Interface
  • Sql Examples
  • Sqlx migrations

v 0.2

  • Redis Example
  • Actix Web Example


Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.


We use SemVer for versioning. For the versions available, see the tags on this repository.


See also the list of contributors who participated in this project.


This project is licensed under the MIT License - see the LICENSE.md file for details


~332K SLoC