Category Archives: NServiceBus

Saga patterns: wrap up

Posted on May 14, 2013 by Jimmy Bogard

Posts in this series: Observer pattern Controller pattern Pattern variations Scaling sagas Routing slips NServiceBus sagas are a simple yet flexible tool to achieve a variety of end goals. Whether it’s orchestration, choreography, business activity monitoring, or just other long-running … Continue reading →

Also posted in Messaging | 3 Comments

Saga alternatives – routing slips

Posted on April 26, 2013 by Jimmy Bogard

In the last few posts on sagas, we looked at a variety of patterns of modeling long-running business transactions. However, the general problem of message routing doesn’t always require a central point of control, such as is provided with the … Continue reading →

Also posted in Messaging | 3 Comments

Scaling NServiceBus Sagas

Posted on March 26, 2013 by Jimmy Bogard

When looking at NServiceBus sagas (process managers), especially at high volume of messages, we often run into two main problems: Deadlocks Starvation This is because of the fundamental (default) design of sagas is that: A single saga shares a single … Continue reading →

Also posted in Messaging, SOA | 7 Comments

Saga implementation patterns – variations

Posted on March 21, 2013 by Jimmy Bogard

In the previous couple of posts, I looked at the two main patterns I run into when looking at sagas: Command-oriented (request/response) in the Controller pattern Event-oriented (pub/sub) in the Observer pattern Of course, these aren’t the only ways our … Continue reading →

Also posted in Messaging, SOA | 6 Comments

Saga implementation patterns – Controller

Posted on March 14, 2013 by Jimmy Bogard

In the previous post on saga implementation patterns, we looked at the Observer pattern. In that pattern, the saga was a passive participant in the business transaction, similar to how many fast food restaurants fulfill orders. But not all food … Continue reading →

Also posted in Messaging, SOA | 17 Comments

Saga implementation patterns – Observer

Posted on March 11, 2013 by Jimmy Bogard

NServiceBus sagas, itself an implementation of the Process Manager pattern, often takes one of two main forms when implemented. It’s not a cut and dry distinction, but in general, I’ve found that saga implementations typically fall into one or the … Continue reading →

Also posted in Messaging, SOA | 11 Comments

NServiceBus, Semantic Versioning and events

Posted on January 31, 2013 by Jimmy Bogard

Something that caught us quite off guard when migrating from the 2.6 version of NServiceBus to the 3.x versions was around how NServiceBus treats assembly versions for publishing messages. When a subscriber expresses intent for a subscription of a message … Continue reading →

| 12 Comments

Messaging Semantics: Ownership

Posted on December 20, 2012 by Jimmy Bogard

In the last post, I covered naming of messages for the different kinds of messages we typically see: Commands Replies Events The names of messages is the first clue I look in to see if boundaries are correct. Often, when … Continue reading →

Also posted in Domain-Driven Design, SOA | 5 Comments

Messaging semantics: names and verbs

Posted on December 6, 2012 by Jimmy Bogard

In most messaging systems I’ve worked with (synchronous or asynchronous), there are three general types of messages that arise: Commands Replies Events Queries can be thought of as a special kind of command where I ask for something and get … Continue reading →

| 7 Comments

NServiceBus and concurrency

Posted on November 1, 2012 by Jimmy Bogard

A while back, Andreas posted on NServiceBus sagas and concurrency. In that post, he described both what to consider and how to change the concurrency model of NServiceBus and how it relates to sagas. One thing that comes as a … Continue reading →

Also posted in NHibernate | 5 Comments