wolverine
wolverine copied to clipboard
JasperFx
Next Generation .NET Command and Message Bus
## Problem * The node assignment and cross-node communication requires a lot of request/response that's today done mostly through the simplistic database control queues -- which is a fancy way...
This bug is a continuation of #966 related to durable local queues. I have a message handler with the following exception policy: ```cs chain.OnException() .Requeue().AndPauseProcessing(15.Minutes()) .Then.MoveToErrorQueue().And(SendFailureMessage); ``` When the handler...
For 3.0. Docs will be done in a follow-up PR. - [x] Add support for Headers exchange - [x] Add support for custom exchange bindings as part of conventional routings...
Bleep it. Use advisory locks and a stateful connection. Eliminate NodeTracker. Do everything at runtime, never trust anything in memory. Try to use the new HTTP transport as possible. Add...
This is in Wolverine just because it needs to go *somewhere*, and because Wolverine is kind of at the top. ## "Problems" * There are some shared framework-y elements like...
This is a placeholder for a longer conversation. There's starting to be more and more boilerplate code for bootstrapping both a headless application or a web application with both Wolverine...
The `params object[] events` argument got us again. User tried to use StartStream(list), and Wolverine/Marten treated that list as one event instead of the individual elements of the list like...
Using it with a client, and I've seen a couple wrinkles to iron out. This will require a little bit of work on the Marten side too. 1. Sometimes, even...
I.e., be able to connect one single application to multiple Rabbit MQ brokers, multiple Azure Service Bus connections, multiple AWS SQS connections Definitely making this part of Wolverine 3.0. Strongly...