I’ve seen that BizTalk 2010 supports the new Mapper Activity for Workflow Foundation (From here: Easy use of mapper and LOB Adapters in WF Designer for AppFabric Applications). The dependency seems to be tied to the AppFabric (hence – IIS?). The question is under what circumstances would you use the mapper activity external from the BizTalk Engine? What advantages does hosting the mapper inside WF Runtime/AppFabric provide that hosting inside of the BizTalk Engine does not? Why not just call a BizTalk Orchestration Web Service directly?
I’ve seen that BizTalk 2010 supports the new Mapper Activity for Workflow Foundation (
Share
BizTalk is a robust and reliable platform that hosts your Business Processes and performs transformations. To this end, it includes a SQL Server database that, among other things, provide persistance to ensure resilience in the face or hardware failures or software crash.
Because of this, BizTalk processes are considered heavyweight and it is usually difficult to achieve very low latency with BizTalk.
On the contrary, WF workflows hosted in IIS do usually provide lower latencies than BizTalk equivalent. However, WF does not provide, out of the box, a streaming XSLT transform engine, suitable for processing large messages without exhausting all available server resources.
That is why using the efficient streaming BizTalk mapper inside a lightweight WF workflow that does not incur the perdormance overhead of being persisted to the database makes sense in certain cases.