Little update since the last check in on Wolverine 5.0. I think right now that Wolverine 5.0 hits by next Monday (October 6th). To be honest, besides documentation updates, the biggest work is just pushing more on the CritterWatch backend this week to see if that forces any breaking changes in the Wolverine internals.
What’s definitely “in” right now:
- The “Partitioned Sequential Messaging” feature work that we previewed in a live stream
- Big improvements and expansion to Wolverine’s interoperability story against NServiceBus, MassTransit, CloudEvents, and whatever custom interoperability folks need to do
- A first class SignalR transport which is getting used heavily in our own CritterWatch work
- A first class Redis messaging transport from the community
- Modernization and upgrades to the GCP Pubsub transport
- The ability to mix and match database storage with Wolverine for modular monoliths
- A bit batch of optimization for the Marten integration including improvements for multi-stream operations as our response to the “Dynamic Boundary Consistency” idea from other tools
- The utilization of System.Threading.Channels in place of the TPL DataFlow library
What’s unfortunately out:
- Any effort to optimize the cold start times for Marten and Wolverine. Just a bandwidth problem, plus I think this can get done without breaking changes
And we’ll see:
- Random improvements for Azure Service Bus and Kafka usage
- HTTP improvements for content negotiation and multi-part uploads
- Yet more improvements to the “aggregate handler workflow” with Marten to allow for yet more strong typed identifier usage
The items in the 3rd list don’t require any breaking changes, so could slide to Wolverine 5.1 if necessary.
All in all, I’d argue this turned out to be a big batch of improvements with very few breaking API changes and almost nothing that would impact the average user.
The Shade Tree Developer 