Author Archives:

Eventual consistency in REST APIs

Posted on May 15, 2013 by Jimmy Bogard

Not picking on an API in particular, but…wait, yes I am. Octopus (an awesome product) has a proposed API on GitHub, and one of the things it describes is how to deal with the fact that the backend is built … Continue reading →

Posted in REST | 6 Comments

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 →

Posted in Messaging, NServiceBus | 1 Comment

Ditching two-phased commits

Posted on May 9, 2013 by Jimmy Bogard

I’ve had a love-hate relationship with two-phased commits during my years with messaging. Even if MSDTC was free to set up, it doesn’t come free in terms of throughput. Most people run into 2PC in messaging because because queueing systems … Continue reading →

Posted in Messaging, SOA | 11 Comments

Messages, data and types

Posted on May 1, 2013 by Jimmy Bogard

One concern I receive quite a bit from folks new to messaging, especially those coming from SOAP and WCF land, is how to preserve the convenience of proxy classes and data contracts that can be shared amongst multiple clients. The … Continue reading →

Posted in Messaging, SOA | 6 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 →

Posted in Messaging, NServiceBus | 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 →

Posted in Messaging, NServiceBus, 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 →

Posted in Messaging, NServiceBus, 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 →

Posted in Messaging, NServiceBus, SOA | 17 Comments

Elaborating on “it depends”

Posted on March 12, 2013 by Jimmy Bogard

On the discussion on “When should I test?”, I followed up with a conversation: When it provides value. When is that? It depends. And it truly does depend. But upon what? That’s trickier to answer – and there is no … Continue reading →

Posted in Agile, TDD | 5 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 →

Posted in Messaging, NServiceBus, SOA | 11 Comments