Fast storage for every claim and hand-off.
teleon.dev/docs/queues-db is the high-write database cell behind the queue broker. It stores task rows, active leases and the graph state that passes batons between queues.
The broker reads task rows; the lease store owns the narrow lease table; edges record every hand-off.
What it does
Built for writes
Claims, heartbeats and submits are small writes, tuned for high input and output rates.
Graph state kept
Each hand-off between queues is recorded as an edge with its status.
Leases apart
Active leases live in a narrow table beside the task rows for quick updates.
The contract
The cell exposes tables to the broker and lease store; clients reach it through those services.
queue_broker_schemateleon_dual_track_request/v1
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/health | RING-3 | Read the cell's health and lag | |
GET | /v1/schema | RING-1 | Read the cell's tables and versions |
Listed paths appear in the service’s published files today. In the one-host plan every path here is served under api.teleon.dev/v1/queues-db.
How it connects
For agents
Give your agent the read-only guide first. It reports back before any write.
Words on this page
- Partition
- One slice of a large table, chosen by a key such as site or queue, so reads and writes stay fast.
- Lease
- A time-limited claim on a task. The worker holding the lease finishes it or the lease expires and the task returns.
- Baton
- The hand-off between queues: when one step finishes, its output becomes the next queue's input row.
- Sister track
- The improvement track that runs beside each database: it tunes priorities, synonyms and steps behind holdout checks.