Summary

In this chapter, we looked at a variety of orchestration usage scenarios that exploit BizTalk in a service-oriented fashion. Through the use of dynamic ports and direct binding, we can create very loosely coupled processes that are capable of reuse. By not directly connecting a batch of related orchestrations but rather relying on external routing rules, we make our orchestration act like encapsulated services whose execution sequence can be determined on the fly. And lastly, by leveraging untyped messages in orchestrations, we explored how to create reusable and flexible orchestrations that do not require changes to be made as more message types are implemented and need to be handled by said orchestrations.

In the next chapter, we'll look at how to take these service-oriented BizTalk artifacts and effectively version them so that new capabilities can be supported while causing minimal impact to existing clients.