Expand description
Queue / Deque Storage Module
FIFO/LIFO message queue with:
- Push/Pop from both ends (deque)
- Consumer groups with acknowledgment
- Dead-letter queue support
- Priority queue mode
- Per-message TTL
Modules§
- consumer_
group - Consumer Groups for Queue
- deque
- Core Queue / Deque implementation
- mode
- presence
- Queue consumer presence — issue #742.
Structs§
- Consumer
Group - A consumer group manages message delivery and acknowledgment for a set of consumers reading from the same queue.
- Consumer
Presence - One row of presence state, returned by
snapshot. - Consumer
Presence Registry - Process-local registry of consumer presence. Cheap mutex + small hashmap is the right shape: writes are O(1), reads are a single snapshot copy, and the cardinality is bounded by the operator’s worker fleet (typically dozens, not thousands).
- Pending
Entry - A pending message awaiting acknowledgment
- Queue
Store - Core queue data structure supporting FIFO, LIFO, and priority modes.
Enums§
- Presence
State - Lifecycle bucket derived from
last_seen_age_msvs the configuredttl_ms. Snapshot consumers (Red UI, virtual tables) read this flag and never re-derive the rule. - Queue
Mode - Queue
Side - Which end of the queue to push/pop from
Constants§
- DEFAULT_
PRESENCE_ TTL_ MS - Default heartbeat budget — a consumer is considered active for this long after its last beat. Operators can override per server via the runtime config; the registry itself is agnostic and takes the budget as an argument on every read path.