wolverine

Wolverine

Wolverine is a Next Generation .NET Mediator and Message Bus. Check out the documentation website at https://wolverinefx.net/.

Support Plans

While Wolverine is open source, JasperFx Software offers paid support and consulting contracts for Wolverine.

Help us keep working on this project

Become a Sponsor on GitHub

Working with the Code

To work with the code, just open the wolverine.sln file in the root of the repository and go. If you want to run integration tests though, you'll want Docker installed locally and to start the matching testing services with:

docker compose up -d

There's a separate README in the Azure Service Bus tests as those require an actual cloud set up (sorry, but blame Microsoft for not having a local Docker based emulator ala Localstack).

Branches

This repository follows a major-line branching strategy:

• main — Active development for Wolverine 6.0, currently published as WolverineFx 6.0.0-alpha.* pre-release packages. Expect breaking changes and dependency bumps to in-development JasperFx 2.0-alpha packages. Day-to-day work, new features, the cold-start / runtime-perf pass and the AOT pillar all land here. See CHANGELOG.md for the cumulative 6.0 inventory and the migration guide for the at-a-glance table of changed defaults / removed APIs / moved namespaces.
• 5.0 — Maintenance branch for the Wolverine 5.x line, branched from the V5.39.0 tag. Receives bug fixes only — no new features and no breaking changes. Patch releases (5.39.1, 5.39.2 …) off the 5.x line ship from this branch until 6.0 is generally available.
• archive/cloudevents-attempt-2025 — Preserved, abandoned. An incomplete CloudEvents-for-SQS-and-SNS feature branch from August 2025 that never merged. Kept for historical reference only.

Older release-specific branches (e.g., 4.0, release/5.30, 5.36) exist for in-flight or completed work on prior versions and are not active development surfaces. New contributions should target main. Backport candidates for the 5.x line can be opened against 5.0 after the corresponding PR has merged to main.

Contributor's Guide

For contributors, there's a light naming style Jeremy refuses to let go of that he's used for gulp 20+ years:

1. All public or internal members should be Pascal cased
2. All private or protected members should be Camel cased
3. Use _ as a prefix for private fields

The build is scripted out with Nuke in the /build folder. To run the build file locally, use build with Windows or ./build.sh on OSX or Linux.

Documentation

All the documentation content is in the /docs folder. The documentation is built and published with Vitepress and uses Markdown Snippets for code samples. To run the documentation locally, you'll need a recent version of Node.js installed. To start the documentation website, first run:

npm install

Then start the actual website with:

npm run docs

To update the code sample snippets, use:

npm run mdsnippets

History

This is a little sad, but Wolverine started as a project named "Jasper" way, way back in 2015 as an intended reboot of an even older project named FubuMVC / FubuTransportation that was a combination web api framework and asynchronous message bus. What is now Wolverine was meant to build upon what we thought was the positive aspects of fubu's programming model but do so with a much more efficient runtime. Wolverine was largely rebooted, revamped, and renamed in 2022 with the intention of being combined with Marten into the "critter stack" for highly productive and highly performant server side development in .NET.