Architecture and Sizing


hi all,

i know impossible question answer, have question around architecture of biztalk solution needs process 160,000 messages day, although 4 message exchanges complete "transaction" has complete within 10 seconds (not including external interface latency), 40,000 total transactions.

basically message sizes small, there map on incoming message , on outgoing message , orchestration pretty doing correlation. there little bit of bam going on monitor throughput , transit times. message transfer via wcf endpoints.

i've explained approach of start smaller number of servers , scale out if necessary i've been told need provide definitive solution.

tempted 2 servers, 1 receive , 1 for transmit and clustered sql, not sure. if has guidelines that'd appreciated, i'm happy overcook if necessary!

cheers,


cd

not 6, 3. 2 of these configure clustered/nlb receive, decide run processing under separate hosts across 3 or two. use separate send host instance , run on same set of two/three servers doing processing.

regards.



BizTalk Server  >  BizTalk Server General



Comments

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

job syspolicy_purge_history job fail in sqlserver 2008

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'