In this chapter, we introduced the need for the use of the saga design pattern as it applies to NSB. We discussed some of the basic features and uses of NSB, as an ESB framework for SOA development. It adds quality to software as a framework standard, with many extensions for logging, security, reporting, and message handling between services. The flow of NSB is the automation of the backend and the decoupling from the frontend, so that automation can occur with services that have message flow from end to end.

NSB supports many design patterns that make up the ESB. The saga pattern provides the means to persist message data, which allows for end-to-end workflow. It can easily respond to the originator of the message, thereby updating the status of an end-to-end flow. The saga data object saves the state of the message to allow services to change the state as the message changes when it flows from end to end in the NSB. NSB solves many design issues, including the need for high availability and behavior changes based on messages for the flow of the end-to-end design. We also discussed many more patterns.

In the next chapter, we will discuss saga architecture.