In this podcast we&rsquo;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&rsquo;ll compare solutions based on .NET 3.5 and on NServiceBus&ndash;covering aspects such as transactions and persistent time-outs. </p>

InformationWeek Staff, Contributor

November 2, 2008

1 Min Read

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 with the next version of WCF. I also have been listening to your podcasts and reading your blog posts about NServiceBus where you talk about long-running workflows. It sounds like both of these technologies are trying to solve the same problem.

Do durable services do away with long-running workflow? If so, does that mean we don’t need Workflow Foundation either? If not, what is the connection between them.

If you could shed some light on the matter that would be great.

Suresh

Download

Download via the Dr. Dobb’s site

Or download directly here

Additional References

Want more?

Check out the “Ask Udi” archives.

Got a question?

Send Udi your question to answer on the show.

Never Miss a Beat: Get a snapshot of the issues affecting the IT industry straight to your inbox.

You May Also Like


More Insights