Jeremy D. Miller
Jeremy D. Miller
Might require some work on the Marten side of things. I think I'd want an `ISessionFactory` where the T could be Jasper's `IExecutionContext`
Might be cool on each handler to see what the error handling policies are
Today all the routing is done based on message type. Analyze if there's any value in doing this by choosing the message route based on the data of the message...
See https://martendb.io/configuration/optimized_artifact_workflow.html. Or really, just make this automatic.
Just based on message ids
No particular analysis yet. Honestly gonna check out how MassTransit does this first. BatchedSender is probably a helper here.
I dropped it out of the solution. Huge PITA because it can't run locally, only in the cloud.
There is an existing Kafka transport that's not part of the solution right now, and would need to be "modernized" to the 2.0 Transport/Endpoint abstractions
Inline RequestAndWait(CancellationToken) : Task, Don't want to do that, but probably necessary for some users.
Need more context here. This is going to be used to standardize the workflow we built as custom code for a client to do acknowledgements about success or failure of...