Sign in to confirm you’re not a bot
This helps protect our community. Learn more

Wolverine: Your Next Messaging Library

JetBrains
210K subscribers
<__slot-el>
<__slot-el>
12K views Streamed 2 years ago #dotnet #jetbrains #CQRS
Wolverine is a new framework for local command handling and asynchronous messaging between processes in .NET. Great, but there are several mature tools like that in .NET, so what's different enough to make this worthwhile? First, Wolverine has a unique approach to command handlers that allow developers to write the simplest possible code and adapt to your code instead of forcing you to use crufty framework-y constructs. As you’d expect, Wolverine has a strong middleware strategy for dealing with cross-cutting concerns but does so in a much more efficient way that avoids the memory bloat issues that degrade the performance of compet …...more
...more
Wolverine: Your Next Messaging Library
Wolverine is a new framework for local command handling and asynchronous messaging between processes in .NET. Great, but there are several mature tools like that in .NET, so what's different enough to make this worthwhile? First, Wolverine has a unique approach to command handlers that allow developers to write the simplest possible code and adapt to your code instead of forcing you to use crufty framework-y constructs. As you’d expect, Wolverine has a strong middleware strategy for dealing with cross-cutting concerns but does so in a much more efficient way that avoids the memory bloat issues that degrade the performance of competing tools in .NET. Wolverine is absolutely meant for real-world development, so it comes out of the box with strong instrumentation. In this talk, I’ll show the out-of-the-box integration with .NET logging, Open Telemetry tracing, and opt-in performance metrics. Being a newer tool, it completely embraces the modern .NET stack, meaning it's easily integrated into any .NET project type that is bootstrapped through the generic host mechanism. Paired with its optional integration with Marten, Wolverine is meant to be a highly effective framework for applications that use CQRS and Event Sourcing. In this talk, we’ll see how Wolverine can remove most of the repetitive code that CQRS with Event Sourcing can often cause. We’ll also examine how integrating Marten opens up easier Event Driven Architecture strategies. Lastly, Wolverine is again meant for real-world development, so we’ll look at how it easily fits into both unit and integration testing strategies. Speaker: Jeremy D. Miller Jeremy Miller is the Senior Director of Software Architecture at MedeAnalytics. Jeremy began his software career writing "Shadow IT" applications to automate his tedious engineering documentation, then wandered into software development because it looked more fun. Jeremy is heavily involved in open-source .NET development as the lead developer of Marten, Wolverine, Lamar, Alba, and other projects in the JasperFx family. Jeremy occasionally manages to write about various software topics at jeremydmiller.com. 0:00 Introduction 2:06 Wolverine 3:22 Why/what/how Wolverine? 6:40 Hello world demo 20:14 Messaging middleware 26:20 Durable inbox/outbox and persistence 34:00 Error handling 42:25 External messaging 45:09 Testing support 52:24 Clone and go 55:38 The "Critter stack" 1:03:08 Q&A 1:12:00 Wrap-up Links: https://jeremydmiller.com https://wolverinefx.net https://github.com/jasperfx/wolverine #dotnet #jetbrains #CQRS

Follow along using the transcript.

JetBrains

210K subscribers