两个工作流：什么时候选择BizTalk，什么时候选择WWF？微软人士给了一个简单的判断原则

So what about BizTalk and Windows Workflow Foundation? Did you bet on the wrong horse by choosing BizTalk Server? No you didn't. BizTalk Server is, was, and will be the right architecture for business process and integration on Windows. To properly serve the needs of business process and integration you need a "man in the middle" server that adapts, routes, tracks, manages, scales and has all the appropriate BPM capabilities such as BAM. Windows Workflow Foundation gives you none of that. On the other hand there are many scenarios that Windows Workflow Foundation is useful outside of business process and integration such include page-flow in ASP.NET web applications, workflow within line of business applications that ISVs build, workflow within Office. By targeting ISVs primarily the Windows Workflow Foundation technology can be embedded within these applications.

Put simply:

A. Workflow within applications = Windows Workflow Foundation

B. Workflow across applications = BizTalk Server

I love working with the press, but on one or two occasions some "selective editing" has provided some out of context quotes. Let me reverse the situation and end on my favorite part of Oliver's article "In fact, the synergy of [Windows Workflow Foundation] and BizTalk will probably make you look like a visionary". You bet we are working hard to make that 100% a reality.

就是说，
应用程序内部的工作流 使用 WWF
应用程序之间的工作流 使用 biztalk

这是一个曾经非常迷惑的问题，看来大家都关心这个问题。

转载：
http://blogs.msdn.com/scottwoo/archive/2005/10/10/479331.aspx