Book Image

SOA Patterns with BizTalk Server 2009

By : Richard Seroter
Book Image

SOA Patterns with BizTalk Server 2009

By: Richard Seroter

Overview of this book

SOA is about architecture, not products and SOA enables you to create better business processes faster than ever. While BizTalk Server 2009 is a powerful tool, by itself it cannot deliver long-lasting, agile solutions unless we actively apply tried and tested service-oriented principles. The current BizTalk Server books are all for the 2006 version and none of them specifically looks at how to map service-oriented principles and patterns to the BizTalk product. That's where this book fits in. In this book, we specifically investigate how to design and build service-oriented solutions using BizTalk Server 2009 as the host platform. This book extends your existing BizTalk knowledge to apply service-oriented thinking to classic BizTalk scenarios. We look at how to build the most reusable, flexible, and loosely-coupled solutions possible in the BizTalk environment. Along the way, we dive deeply into BizTalk Server's integration with Windows Communication Foundation, and see how to take advantage of the latest updates to the Microsoft platform. Chock full of dozens of demonstrations, this book walks through design considerations, development options, and strategies for maintaining production solutions.
Table of Contents (18 chapters)
SOA Patterns with BizTalk Server 2009
Credits
About the author
About the reviewers
Preface
Index

Why orchestration?


At its core, orchestration is an executable business process that acts upon messages passing through the service bus. In the BizTalk world, orchestration has both a design-time and runtime aspect. At design-time, a developer uses a predefined palette of activities, which are linked together to form a business process. The runtime orchestration engine is a server service which coordinates all aspects of orchestration execution ranging from starting up and terminating orchestrations to load balancing and monitoring the orchestration processing health.

In many cases, a purely messaging-oriented solution is exactly what our situation calls for. However, we often need the flexibility to introduce a long-running, stateful interception of messages which may contain business logic, control flow, data processing, exception handling and transactions. This is the value of orchestration. What is the value of orchestration in a service-oriented architecture? Let's look at some of the...