A challenging question…
I see only one good reason.
.m
I see only one good reason.
.m
I see only one good reason.
.m
Mauro is a Solution Architect in Particular Software, the makers of NServiceBus. He spends his time helping developers build better .NET systems leveraging Service Oriented Architecture (SOA) principles and message-based architectures.
- A small ServiceControl maintenance utility
- Someone says event, and magically, coupling goes away
- I gotta tell you: CQRS doesn't imply Event Sourcing
- Mattox: simple, pre-configured NServiceBus endpoints
- Compensation is all around us
- Define messages as POCO, interfaces, or records. Does it really matter?
- The power of timeouts to compensate for failures and other tales
- Append-only models: The why, the when, and the how
I recently had the opportunity to deliver talks at the following events:
Each event lists links to slides, demos, recording, and additional material. Check them out.