Synchronous service intermediary in BizTalk


we use biztalk server 2009 service intermediary in synchronous scenarios. today use biztalk message-bus typical asynchronous publish-subscribe scenarios, big success. reason why use biztalk server service intermediary is, give possibility mapping of requests/responses , use broad variety of adapters , of course monitoring using bam.

we have made proof-of-concept on synchronous scenarios , works fine, latency in periods of heavy-load isn’t acceptable because of biztalk’s pub/sub architecture, synchronous messages aren’t prioritized. have tried following without success:

·         working send port priority

·         assign synchronous work dedicated host

·         make load-test both small , big files, no differences on result

our main problem can’t find way prioritize asynchronous communication on asynchronous.

my question now; have experience or best-practices setting / using biztalk in synchronous scenarios? in environments used heavy asynchronous communication in periods?

thank you!   

 

i've had lot of success biztalk synchronous services.  spend lot of time tuning , use separate group 1 asynch.  real issue need balance throughput , latency.  darren jefford's book professional biztalk server 2006 goes pretty deep.  good. 

tuning biztalk people not know well, intricate , takes long time , careful planning right.  takes knowledge of sql server, windows os, tcp/ip, , san (just mention few of them).  should able sub 100ms response times, it's gonna take work there , limit how many concurrent requests can serve.  keep in mind though in enterprise applications have 1-2% of users making requests @ given time. 

kind regards,
-dan


BizTalk Server  >  BizTalk Server General



Comments

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

Catalog Staging

How to Share webservice object to all user