Do you have a system where you think would be a good fit for a CQRS architecture that also uses Event Sourcing for at least part of its persistence strategy? Are you intimidated by the potential complexity of that kind of approach?
Fear not, using a combination of the Postgresql-backed Marten (martendb.io) library for event sourcing and its newer friend Wolverine (wolverine.netl...) for command handling and asynchronous messaging, I'll show you how you can quickly get started with both CQRS and Event Sourcing. Once we get past the quick start, I'll show you how the Critter Stack's unique approach to the ""Decider"" pattern will help you create robust command handlers with very little code ceremony while still enjoying easy testability.
Moving beyond basic command handling, I'll show you how to reliably subscribe to and publish the events or other messages created by your command handlers through Wolverine's durable outbox and direct subscriptions to Marten's event storage.
Download .NET 8 - aka.ms/get-dot...
Hack Together - aka.ms/hacktog...
Learn collection - aka.ms/learn-d...
.NET 8 Survey - aka.ms/dotnet-...
Local Events - aka.ms/dotnetc...
Hero blog - aka.ms/dotnet8...
Blog: aka.ms/dotnet/...
Twitter: aka.ms/dotnet/...
TikTok: aka.ms/dotnet/...
Mastodon: aka.ms/dotnet/...
LinkedIn: aka.ms/dotnet/...
Facebook: aka.ms/dotnet/...
Docs: learn.microsof...
Forums: aka.ms/dotnet/...
🙋♀️Q&A: aka.ms/dotnet-qa
👨🎓Microsoft Learn: aka.ms/learndo...
#dotnet
4 окт 2024
