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. Finally, we saw that there are creative ways to listen in on the traffic of the message bus and seek out aggregate business events that may provide early warning insight into critical business conditions.
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.