-
Notifications
You must be signed in to change notification settings - Fork 54
Transport Native Support #629
Comments
It doesn't make sense. Use native dead letter queue functionality for both Rabbit MQ and Azure Service Bus. Ugh, this might call into question the entire listener approach to use much more native transport functionality. Might mean that the |
As we've discussed I second these changes. The transports have robust functionality built in to deal with ordered delivery of messages and retry/dead letter logic. In particular, when ordering is a requirement we need to make sure the message is handled by the routed handler before acknowledging the message and reading the next from the transport. Even if we could guarantee ordered processing of the internal incoming jasper queue I think that would fall apart in a load balanced situation where multiple instances were processing a single stream/topic. I did some playing around with this. Similar to how we pushed some logic from the |
Should have done this before, but here we are and we need this:
Rabbit MQ
Azure Service Bus
Pulsar
Kafka
|
I'm declaring success here. |
Go over it all and see if it still makes sense.
The text was updated successfully, but these errors were encountered: