#task-queue #task-execution #task-scheduling #task #queue #surrealdb #background-task

kafru

kafru is a Python Celery-inspired queuing library for Rust, using cron for scheduling and SurrealDB for storing queues, metrics, and schedules

1 unstable release

new 0.1.13 Nov 7, 2024
0.1.11 Nov 7, 2024
0.1.5 Sep 27, 2024

#225 in Asynchronous

Download history 307/week @ 2024-09-05 165/week @ 2024-09-12 14/week @ 2024-09-19 196/week @ 2024-09-26 10/week @ 2024-10-03 6/week @ 2024-10-10 4/week @ 2024-10-17 220/week @ 2024-10-31

239 downloads per month

MIT license

8MB
2K SLoC

kafru

kafru is a Rust crate designed for efficient task queue management, inspired by the task queue systems found in other programming environments. The name "kafru" is derived from the "Kafra" system in the popular game Ragnarok Online.

This library offers robust background task execution with parallel processing through multithreading, enabling tasks to run concurrently and efficiently. Additionally, kafru features advanced scheduling capabilities, utilizing cron for precise task timing. It integrates seamlessly with SurrealDB for comprehensive management of queues, metrics, and schedules, ensuring reliable and organized task execution.

Cute cat GIF

Features

  • Task Registry: Manage and organize a collection of structs designed for task execution.
  • Scheduler: Utilize cron-based scheduling to define when tasks are pushed to the queue, with options to set start and end times.
  • Queue: Maintain a list of tasks awaiting execution.
  • Worker: Execute tasks from the queue, referencing the task registry to determine the appropriate struct for each task.
  • SurrealDB Integration: Store and manage scheduling details, queue information, and metrics using SurrealDB.

Installation

cargo add kafru

Usage

1. Run SurrealDB

For testing, you can start SurrealDB using an in-memory database:

cargo test -- --nocapture --test-threads=1
surreal start -u kafru_admin -p kafru_password -b 0.0.0.0:4030 --allow-all memory

For running SurrealDB in file mode, refer to the SurrealDB documentation.


2. Environment Variables

The following environment variables can be used to configure the database:

Key Description Default Value
KAFRU_DB_USERNAME The database username. kafru_admin
KAFRU_DB_PASSWORD The database password. kafru_password
KAFRU_DB_PORT The port number of the database. 4030
KAFRU_DB_HOST The database host or IP address. 127.0.0.1
KAFRU_DB_NAMESPACE The database namespace, useful for separating production and testing databases. kafru
KAFRU_DB_NAME The database name. kafru_db

Registering Task Structs to the Task Registry

The task registry stores a collection of task structs that contain the logic to be executed.

3. Create a Task Struct

  • Your struct must implement the TaskHandler trait.
  • Define the code to execute within the async fn run(&self, _params: std::collections::HashMap<String, Value>) -> Result<(), String> method.

Sample

use async_trait::async_trait;
use kafru::task::TaskHandler;
use serde_json::Value;
use std::collections::HashMap;

pub struct MySampleStruct;

#[async_trait]
impl TaskHandler for MySampleStruct {
    async fn run(&self, _params: HashMap<String, Value>) -> Result<(), String> {
        let x = 1; // Replace this with your logic.
        let total = x + 1;
        // Perform your task logic here.
        Ok(())
    }
}

4. Register the Struct to the Task Registry

  • After defining the task struct, register it in the task registry by providing a name for the struct.

Sample

use async_trait::async_trait;
use kafru::task::{TaskHandler, TaskRegistry};
use serde_json::Value;
use std::collections::HashMap;

pub struct MySampleStruct;

#[async_trait]
impl TaskHandler for MySampleStruct {
    async fn run(&self, _params: HashMap<String, Value>) -> Result<(), String> {
        // Task logic here.
        Ok(())
    }
}

#[tokio::main]
async fn main() {
    let mut task_registry: TaskRegistry = TaskRegistry::new().await;
    task_registry.register("mytesthandler".to_string(), || Box::new(MySampleStruct)).await;
}

5. Running the Worker and Scheduler via the Manager

To execute tasks using both the worker (watcher) and the scheduler, follow these steps:

use std::sync::Arc;
use kafru::manager::Manager;
use kafru::task::TaskRegistry;

// Initialize the Manager struct.
let mut manager: Manager = Manager::new().await;

// Initialize the Task Registry struct and register the task.
let mut task_registry: TaskRegistry = TaskRegistry::new().await;
task_registry.register("mytesthandler".to_string(), || {
    Box::new(MySampleStruct {
        message: "Hello World".to_string(),
    })
}).await;

// Share the task_registry using Arc for thread safety.
let task_registry: Arc<TaskRegistry> = Arc::new(task_registry);

// Run the Worker, specifying the queue name, number of threads, the task registry, and task poll interval (in seconds).
let _ = manager.worker("default".to_string(), 5, task_registry.clone(), 15).await;

// (Optional) Run the Scheduler by specifying the scheduler name and interval (in seconds).
let _ = manager.scheduler("kafru_test_scheduler".to_string(), 5).await;

// Optionally, wait for both the worker and scheduler to finish. This will prevent the function from exiting prematurely.
let _ = manager.wait().await;

Explanation

  • Task Registration: Registers a task struct (MySampleStruct) in the task registry.
  • Task Registry: Shared using Arc to enable safe concurrent access in a multi-threaded environment.
  • Worker: Runs tasks from the queue, controlled by parameters such as:
    • queue_name: Name of the queue to pull tasks from.
    • num_threads: Number of threads to handle task execution.
    • task_registry: Registry that contains the task structs.
    • poll_interval: Polling interval (in seconds) to check for new tasks.
  • Scheduler: (Optional) Runs scheduled tasks at specified intervals, similar to cron jobs.
  • Join: Ensures that both the worker and scheduler keep running without the program exiting prematurely.

Code Documentation

For detailed documentation, visit docs.rs/kafru.

License

This project is licensed under the Custom License Agreement. See the LICENSE file for details.

Contributing

Contributions are welcome! Please refer to the CONTRIBUTING.md file for guidelines.

Contact

For questions or feedback, you can reach me at jpmateo022@gmail.com.

Dependencies

~75MB
~1.5M SLoC