Understanding the layers of a BizTalk solution

Continuing our train of thought about partitioning a BizTalk solution, we now arrive at a very familiar topic in system architecture: logical structure. From a logical standpoint, a properly constructed BizTalk solution, like any good software solution, stresses the separation of concerns in an effort to control dependencies. This throws off a lot of people new to BizTalk because it involves concepts from both the object-oriented and message-oriented theories of software development.

The following proximity diagram depicts how the layers in a BizTalk solution should interact. Only layers that actually touch each other should be interacting in any way. The intention from this should be quite clear; ...

Get Microsoft BizTalk Server 2010 Patterns now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.