Our first case study on Microsoft patterns & practices!

Chris Han — Fri, 02 Jun 2006 12:49:00 GMT

http://geekswithblogs.net/chrishan/articles/80454.aspx

Although the story only mentions the external apparel we did with ASP.NET 1.1/2.0, the biggest challenge in terms of architecture design we are constantly facing is to balance between the desire of SOA's flexibility/maintainability/reusability and the performance demand by such as a high volume system.

Our client is in fact a typical Application Service Provider in financial circle.(one of those actually survived ASPs.) Their business model has born with a demand of integration. Both integrate with different partners and with a whole spectrum of technologies from legacies to cutting ages, you name it we got it. That’s where the BizTalk gets in the play.

Due to the size of the messages and the processing time restriction, we are trying to use parallel processing as much as possible. The top utilized integration patterns in this project are:

· Scatter-Gather

· Splitter

· Aggregator / Convey

The management patterns implemented are primarily:

· Wire Tap

· Control Bus

I find to implement Wire Tap in pipeline component is very interesting. The challenge here is that we need some information on the incoming message even before it hits the message box, meanwhile you are suppose to process the message here in a streaming manner. A pipeline component is a perfect fit because you don’t have to stop the processing of business messages. All you need to do is to get a copy of the incoming message by pInMsg.BodyPart.Data. From there, it’s all old world you used to.

SOA ain't born of air.

chrishan — Sun, 02 Oct 2005 17:03:00 GMT

I'm reading Pat Helland's article: Data on the Outside vs. Data on the Inside. It's much like a history of software architecture that many of us have gone through. I'm always amazed by the history because you can really predict the future by looking at the patterns it repeats itself again and again. The problems arise just in different faces perhaps in a different abstraction level or a different view or a different context. But fundamentally, they are same.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/his_2004Main/htm/his_planning_for_transaction_integrator_node_adxt.asp

Architecture!

Our first case study on Microsoft patterns & practices!

SOA ain't born of air.