Reusing BizTalk Mapper

The current project I am involved is using BizTalk 2004. Due to stringent latency requirement against large volume, we have decided to go without BizTalk.
I would like to see a global configuration facility in BizTalk that instructs not to persist anything while doing transfermations or orchestration — even with an atomic / long running scope. This would certainly be a risky proposition yet it would improve response time a lot. Wishful thinking!
Here are a couple of great articles on how to reuse BizTalk maps in .Net app.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s