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

"Oslo"


"Oslo" is the code name for the set of technologies that make up the new modelling platform from Microsoft. The Oslo suite is comprised of a repository which stores models and associated context, a modelling language (codenamed M) that describes the model information, and a tool (codenamed Quadrant) which provides a visual mechanism for interacting with models in the repository. In the Oslo world, a model represents anything from an application to a deployment landscape to a business process. Unlike UML, which is frequently used for describing systems, the Oslo models are meant to both represent abstract concepts and actually be the application itself.

What problem does it solve?

There is rarely a tight correlation between the design of a process and its implementation. Sure, a developer does their best to maintain the spirit of the business process or rule when they write their code, but there is no direct relationship between the modelled processes and the final solution. The ambitious...