Expand description
Core traits and types for the Rustvello distributed task system.
This crate defines the abstract interfaces that all backend implementations must satisfy:
- [
Broker] — message routing between producers and runners - [
Orchestrator] — invocation lifecycle and status management - [
StateBackend] — persistence of invocations and results - [
Runner] — task execution engine - [
ClientDataStore] — external storage for large serialized values
See rustvello-mem for in-memory implementations (testing),
rustvello-sqlite for SQLite (single-host production),
rustvello-redis for Redis, rustvello-postgres for PostgreSQL,
rustvello-mongo / rustvello-mongo3 for MongoDB, and
rustvello-rabbitmq for RabbitMQ.
Modules§
- broker
- call
- Typed call representation bridging task parameters to serialized form.
- client_
data_ store - Client data store — external storage for large serialized values.
- context
- Execution context for tasks running inside a rustvello runner.
- error
- invocation
- Invocation types for tracking task execution.
- logging
- Logging configuration types for rustvello.
- middleware
- Task middleware for pre/post execution hooks.
- observability
- Observability infrastructure for the Rustvello distributed task system.
- orchestrator
- prelude
- reconnectable
- Reconnectable trait for backend connection pools.
- runner
- serializer
- state_
backend - task
- trigger
- Trigger system — backend trait and evaluation logic.
- workflow
- Workflow-related types and utilities.