April 9, 2024
A small ServiceControl maintenance utility
From time to time, I enjoy writing code on the side, like an open-source project. This time, the opportunity came from a support case and the need to ease the customer's life in their daily maintenance tasks.
Someone says event, and magically, coupling goes away
I feel events are used too many times as a hammer to dismantle coupling. Unfortunately, it's gold plating. It might look better, but it'll fire back in the long term and cost more.
I gotta tell you: CQRS doesn't imply Event Sourcing
Too many times, Event Sourcing is presented as the natural companion to CQRS. That's not the case. CQRS doesn't dictate using Event Sourcing. Let's see why.
Mattox: simple, pre-configured NServiceBus endpoints
NServiceBus endpoints support only code-based configuration, which is handy and not always friendly at the same time. But what if we could plug in the superb Microsoft configuration extensions to configure NServiceBus endpoints?
Compensation is all around us
In a message-based system, we might feel a lack of control, especially when in need of compensating changes spread across the system. Fear not! Real life deals with compensation every day! And it's better than rolling back a transaction or deleting some data in the database.
Define messages as POCO, interfaces, or records. Does it really matter?
.NET developers building message-based systems seem to give serialization and surrounding concerns more importance than needed. Let's try to dissect the topic
The power of timeouts to compensate for failures and other tales
There are scenarios when a chatty services relationship seems the only option, with the results of coupling quickly becoming our best friend. Not all hope is lost, we can try to ask different questions to untangle the knot.