Overhaul of the Dead Letter Queue Functionality for 4.0

jeremydmiller commented 8 months ago

Today Wolverine would try to use the database DLQ for any endpoint that isn't Inline

jeremydmiller commented 2 months ago

While the hood is up on Wolverine 3.0. Here's some ideas:

Ability to opt into using a transport's native DLQ functionality for both buffered or durable endpoints. Today, Wolverine would use the database backed DLQ no matter what
Adding more contextual information to native transport DLQ for exception type at the least
Option to make all DLQ messages go to the database backed store. **I think this is going to be necessary for "CritterWatch" anyway
Option to set expiration times on DLQ messages so they're automatically dumped from the database over a certain timeframe. Make that configurable, and opt in or out.

jeremydmiller commented 1 month ago

This will be done as part of the "Critter Watch" product, so drops to 4.0

JasperFx / wolverine