BUZZ QUEUES
Exactly-once delivery. Dead-letter queues. 30-day retention. RESP3 wire protocol -- use any Redis client.
MESSAGE FLOW
A message is written to a named queue with an optional deduplication key. Buzz persists it, assigns a sequence number, and acknowledges in a single round-trip.
Messages are durably stored with 30-day retention. Consumer groups partition messages for parallel processing. Rebalancing is automatic when consumers join or leave.
Consumers pull messages in order. Each message is locked to one consumer at a time. Failed messages retry with backoff, then route to the dead-letter queue.
FEATURES
Server-side deduplication using message fingerprints. Consumers acknowledge or reject. Unacknowledged messages redeliver after a visibility timeout.
Partition messages across consumers for parallel processing. Rebalancing is automatic. Offsets are committed atomically.
Publish once, deliver to many. Topic subscriptions with glob-pattern matching let multiple services react independently.
Buzz speaks RESP3 natively. Connect with any Redis client library. No proprietary SDK required. Existing tooling works out of the box.