We have discussed moving sagas from version 4.0 to version 5.0. Version 5.0 has many more tools and packages that are geared towards Windows Azure, Visual Studio 2012, and .NET 4.5. This enables greater compatibility with Azure development and testing, as well as using Azure SDK tools, and the many tools that Visual Studio 2012 provides. This is definitely a positive sign in the evolution of a saga with Windows cloud computing.

We discussed a credit card approval sample using a saga service and saga data. This example could be used in multiple scenarios: from using the WCF service of a bank to deduct from a credit card to ordering from a catalog. The messages, endpoints, and services are managed by NSB as it maps the state of the messages and ensures their durability. The message flow is an important concept as messages can be sent to different business divisions for their business applications, or handled as separate processes, just as we used an accounting department application...