Operations

Configuring Queues


Assigning Workers to Queues

Each worker polls exactly one task queue, specified via the builder API:

1
use orcher::prelude::*;
2
3
#[tokio::main(flavor = "current_thread")]
4
async fn main() -> Result<()> {
5
// This worker polls the "payments" queue
6
let worker = WorkerBuilder::new()
7
.server_url("http://localhost:50051")
8
.namespace("production")
9
.task_queue("payments")
10
.max_concurrent_workflows(100)
11
.max_concurrent_tasks(200)
12
.build()
13
.await?;
14
15
worker.run().await
16
}

Queue Isolation by Workload

Use separate queues to match workers to their workload characteristics:

1
// CPU-intensive work — deploy on compute-optimized instances
2
let compute_worker = WorkerBuilder::new()
3
.task_queue("ml-inference")
4
.max_concurrent_tasks(10) // Low concurrency for CPU tasks
5
.build().await?;
6
7
// I/O-intensive work — deploy on network-optimized instances
8
let io_worker = WorkerBuilder::new()
9
.task_queue("api-calls")
10
.max_concurrent_tasks(500) // High concurrency for I/O tasks
11
.build().await?;
12
13
// Payment processing — dedicated, high-reliability workers
14
let payment_worker = WorkerBuilder::new()
15
.task_queue("payments")
16
.max_concurrent_tasks(50)
17
.build().await?;

Namespace Isolation

Namespaces provide complete queue isolation for multi-tenancy and environment separation. Two workers polling the same queue name in different namespaces will never receive each other's work:

1
# Development workers
2
ORCHER_NAMESPACE=development ./my-worker
3
4
# Production workers
5
ORCHER_NAMESPACE=production ./my-worker
6
7
# Per-tenant isolation
8
ORCHER_NAMESPACE=tenant-acme ./my-worker

Next Steps