Architecture: BizTalk Pub-Sub - Throttling/Performance/latency


from archituture of pub-sub in biztalk

i have single entry(receiveport) canonical schema[header block , body block<any node> ]. 1 promoted property in header block identify function[business process].

the key busines process associated 5 areas[not expected change frequently].

option 1: receive message in canonical format message db. desired application directly bound msgbox , filter based on promoted property[eg: promoted property=businessprocessa] , needful processing down line.

option 2: have 5 maps on inbound receive port(inbound map)/custom pipeline , based on promoted property transform desired business process schema , dump msgbox db. respective applications subscribe namespace/business process schema , needful processing down line.

question

1. better approach. if tomorrow have more applications wanting subscribe of these messages.

is filter condition of promoted property on message[canonical] or filtering on specific schema[as option2] better route. i'm thinking subscription table take care of subscriptions , whom needs go , option 1 simpler implement/maintain/losely coupled and cost effective. how internal of bts play in subscription scenario this.

any thoughts?


raja

any light on details of how subscription works within biztalk engine--> there nice article charles how subscription works, please have look.

hth,
naushad alam

when see answers , helpful posts, please click vote helpful, propose answer, and/or mark answer
alamnaushad.wordpress.com
new technet wiki "biztalk server: performance tuning & optimization"



BizTalk Server  >  BizTalk Server General



Comments

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

BizTalk Server 2013 Azure VM Log Shipping and HA for hosts

How to Share webservice object to all user