-
Notifications
You must be signed in to change notification settings - Fork 2
Home
Osvaldo Andrade edited this page Feb 12, 2026
·
6 revisions
codeQ is a reactive scheduling and completion service built on persistent queues in KVRocks. Producers enqueue tasks under a command (event type). Workers pull tasks by command, claim ownership via a lease, and then either complete, fail, or nack the task for a delayed retry.
The product intent is simple: keep the queue semantics small and explicit, so workers can be dumb and horizontal scaling is safe. codeQ does not try to "assign work" to workers. Even when push is enabled, codeQ only sends advisory signals that work is available; the worker must still claim through the pull API.
Source: github.com/osvaldoandrade/codeq.
- Overview
- Tasks and Results
- Queue Model
- Sharding
- Leases and Ownership
- Multi-Tenancy
- Authentication and Authorization
- Persistence Engine
- Consensus and Replication
- Cluster-Level Failover
- Deployment Modes
- Architecture Overview