feat: delivery failure reporting for consumer-side DLQ #9

New Issue

GKaszewski · 2026-05-30T01:22:38Z

GKaszewski commented

2026-05-30 01:22:38 +00:00

Closed: The event-driven path (EventPublisher) already gives consumers full control — they receive DeliveryRequested, own retries, and get DeliveryFailed on errors. That's everything needed to build a DLQ. The fire-and-forget path (no publisher) is intentionally fire-and-forget; adding rich failure reporting to it contradicts its purpose. Consumers who need DLQ should use EventPublisher.

**Closed:** The event-driven path (`EventPublisher`) already gives consumers full control — they receive `DeliveryRequested`, own retries, and get `DeliveryFailed` on errors. That's everything needed to build a DLQ. The fire-and-forget path (no publisher) is intentionally fire-and-forget; adding rich failure reporting to it contradicts its purpose. Consumers who need DLQ should use `EventPublisher`.

GKaszewski closed this issue

2026-07-11 08:30:35 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GKaszewski/k-ap#9