Windows Workflow Foundation & BizTalk: Where does it all fit?

The most common question on most developers/technologists minds: Where does this Workflow Foundation fit it and does it replace BizTalk? The answer is a big fat NO and Scott Woodgate tells us why here.

I have included a brief excerpt from his post.

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

Tags: Windows WorkFlow Foundation