We would try to understand this by considering an example wherein we need to create a credit processing application for a bank.
So essentially there would be three applications that needs to be communicated to
a. OracleAPP to provide the customer credit limit
b. CRM to provide the payment status
c. Payment transaction system to find list of pending transactions.
So each of the four parts represents a pattern and a part of the solution: the
a. service interface -- interfacing with the external world; web service or anything else
b. content-based router -- to validate the message and send response accordingly
c. a recipient list -- whom to send the messages to
d. an aggregator. -- collect the responses from the different back end systems
what are the things that are missed out in the solution:
a. message translator
b. how the communication between systems happen
c. nature of the service interface
d. sync or async communication; if it is async we need correlation
So apart from what patterns are mentioned,additional patterns that we ended up using are
a. caching pattern using sso
b. Filter pattern to route it to recipients
In brief we have touched down on some of the soa tenets of biztalk and the patterns it uses.
Next article we would look into ESB
For performance stuff delve into
http://msdn.microsoft.com/en-US/library/hh183979(v=bts.10)
So essentially there would be three applications that needs to be communicated to
a. OracleAPP to provide the customer credit limit
b. CRM to provide the payment status
c. Payment transaction system to find list of pending transactions.
So each of the four parts represents a pattern and a part of the solution: the
a. service interface -- interfacing with the external world; web service or anything else
b. content-based router -- to validate the message and send response accordingly
c. a recipient list -- whom to send the messages to
d. an aggregator. -- collect the responses from the different back end systems
what are the things that are missed out in the solution:
a. message translator
b. how the communication between systems happen
c. nature of the service interface
d. sync or async communication; if it is async we need correlation
So apart from what patterns are mentioned,additional patterns that we ended up using are
a. caching pattern using sso
b. Filter pattern to route it to recipients
In brief we have touched down on some of the soa tenets of biztalk and the patterns it uses.
Next article we would look into ESB
For performance stuff delve into
http://msdn.microsoft.com/en-US/library/hh183979(v=bts.10)
