I’ve been sitting on this post for a while, waiting, before outlining all the kinds of problems durable messaging doesn’t solve, I wanted to have a solution handy. Harry Pierson begins to outline the goodness that durable messaging brings to SOA, and in a later post on idempotence describes in general terms how it ties back into durable messaging and transaction - in essence describing a saga.

“Is it still valid to assume it is more expensive to design a scalable system?”

In Gavin Terrill’s news post on InfoQ, Big Architecture Up Front - A Case of Premature Scalaculation? he covers one of the questions so many of my clients deal with:

“How hard will it be to make it scale later?”

This is a valid question, especially for companies/products just beginning their lifecycle. When the

In this podcast we’ll be discussing the issues around multi-threaded processing of messages by a service, specifically that the processing of message received second may be finished before that of the first. This scenario tends to rear its ugly head at higher levels of load and is critical for correctness in high-scalability environments.

Our long time listener Bill asks:

Hi Udi,

I have a

“Is it still valid to assume it is more expensive to design a scalable system?”

In Gavin Terrill’s news post on InfoQ, Big Architecture Up Front - A Case of Premature Scalaculation? he covers one of the questions so many of my clients deal with:

“How hard will it be to make it scale later?”

This is a valid question, especially for companies/products just beginning their lifecycle. When the

I got this question the other day from one of my long-time readers Bill about nServiceBus and I thought I’d share:

I have a question around processing of messages in proper order.  When leveraging multiple threads to process messages in a message queue, it is possible for the second message in the queue to get processed before the first - especially if the first message is considerably larger

In this podcast we’ll be discussing certain methodologies for migrating an architecture from N-Tier to SOA. We’ll see what parts can be used almost unchanged, and which N-Tier concepts have no place in this new, service-oriented world.

Ketan asks:

Hello Udi,

I am Ketan, working as Analyst Programmer in India. I want some information regarding SOA Architecture. I have visited several blogs and

In this podcast we’ll look at the issues around Durable Services, what makes them stateful or stateless, as well as how WCF and WF can be used to implement them. Finally, we’ll compare solutions based on .NET 3.5 and on NServiceBus–covering aspects such as transactions and persistent time-outs.

Suresh asks:

Hi Udi,

I’ve been reading about the coming “durable services” that will be available