Message Broker 0.4: Shared Queue Semantics
Message Broker 0.4 added shared-queue delivery semantics with claiming, leases, acknowledgement, retries, and dead-letter flows.
Message Broker 0.4 added full shared-queue semantics, giving the product both stream and work-queue behavior.
Added
- Added message claiming with persisted delivery state.
- Added lease and lease-renewal behavior for in-flight work.
- Added ACK and NACK handling.
- Added retry and delayed retry flows.
- Added dead-letter behavior for messages that cannot complete successfully.
- Established shared queues as a substantial second personality alongside durable streams.
Looking Ahead
The next goal for Message Broker was to surround the data plane with operational, security, diagnostic, CLI, and SDK surfaces so teams could evaluate and troubleshoot the broker more realistically.
Notes
This entry records early product history and does not represent current availability, support scope, or production readiness. Current product status and limits remain documented in the product docs.
