Creează un cont pentru a te abona la acest blog și a-i urmări articolele pe pagina Lectură.
-
When an employee corrects the time they started or stopped working in a time-tracking system, a workflow typically notifies their manager or HR that the data has changed.
-
TL;DR: Azure Service Bus does not support autoforwarding from a session-enabled subscription.
-
TL;DR: Most workflows are better off accepting out-of-order delivery and modeling the business process to cope with it.
-
TL;DR: Azure Service Bus can run an old and a new delivery path side by side while you migrate one event stream at a time.
-
TL;DR: Blast radius means how much unrelated traffic is affected when one messaging resource reaches a limit or stops making progress.
-
TL;DR: A single Azure Service Bus topic can be a reasonable starting point for one-to-many messaging.
-
TL;DR: Azure Service Bus can publish one message to a topic and deliver it to multiple consumers.
-
TL;DR: Keep only the benchmarks that protect important hot paths.
-
In part thirteen of this event sourcing series, we expand on set-remove-based bi-temporal events.
-
We return to bi-temporal event sourcing in part twelve of my series on event sourcing.
-
TL;DR: The async model is a contract.
-
TL;DR: A visibility timeout is a lease.
-
In part eleven of this series on event sourcing, we make a small detour to discuss consistency boundaries.