- October 9, 2026A pattern that commits business changes and pending messages together, then publishes the messages asynchronously.
- October 9, 2026A pattern that atomically records message-processing receipts with business changes to handle duplicate deliveries.
- October 9, 2026A message that repeatedly fails processing and can create an endless retry loop without quarantine.
- October 9, 2026A separate queue for messages that fail normal delivery or processing under a defined policy.
- October 9, 2026The distance between a stream consumer's processing position and the data available for it to process.
- October 9, 2026A delivery guarantee that prevents repeat delivery but permits message loss.
- October 9, 2026A delivery guarantee that allows repeated delivery so a lost acknowledgement does not silently discard a message.
