Mike makes an interesting observation about the future of BAM in his post here. I think the scope for confusion and blurring is going to become wider than just BAM though. Microsoft are saying that the purpose of BizTalk is as the “Integration Server” in the jigsaw, while Dublin is the Application Server. Now you can imagine developers building fine grained services hosted inside Dublin and BizTalk providing both ESB and technology/protocol Integration services as well as orchestration but what about the common requirements like a Service Registry or a Rules Engine? UDDI 3.0 will ship with BizTalk 2009 (UDDI previously shipped with W2K3) and both BizTalk and WF have rules engines. As we move forward the picture will hopefully become clearer as to what will merge, what will remain separate and where the various offerings position themselves.