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

Service-oriented endpoint patterns


What can we do to make our endpoints as service-oriented as possible? We can retain our focus on reusability, abstraction, interoperability, and loose coupling in order to accomplish this. One way to do this is embrace data mapping and not be hamstrung by the idea that the bus should only accept a single canonical schema. If we don't force service callers to all implement a specific data format, we can instead grow our set of callers organically and bring on new clients with ease.

Building reusable receive ports

One key way to make our services as interoperable as possible is to offer a range of inbound transmission channels. While it would be ideal if all our service clients were running the latest versions of the .NET framework, in reality, we are frequently interacting with either dated or cross-platform service consumers. Also, while we may have all service consumers on the same platform, they may all define a particular data entity in slightly different...