One of the major conclusions of this articwl is that ESB Pattern realised in the ESB systems does not fit 'as implemented' with Business Services. Particularly, ESB may be used in between Business Service Consumer and Business Service only if: 1) the ESB system takes on certain business responsibilities and becomes a business intermediary player, or 2) fully incorporated into either Consumer or Service, i.e. diapperas as an independent entity from the clonsumer-service interaction. The article provides some explanations of why is statements 1 and 2 are true.
- Michael ________________________________ From: Gervas Douglas <[email protected]> To: [email protected] Sent: Sat, August 28, 2010 2:27:50 PM Subject: [service-orientated-architecture] Michael on Patterns You can find this article in full at: http://www.infoq.com/articles/patterns-soa-business-services Gervas <<Along the evolutionary path through centuries, the Mankind has found that we need some things stable, immutable, and even ‘untouchable’ to grasp the other constantly changing things. The examples of such immutable things include religion postulate, mathematical axioms and the Earth shape. Nonetheless, sometimes, the knowledge acquired in the evolution pushed us to change even the immutable ones. Such things have happened, e.g., with mathematical axioms, particularly, with the Euclid’s geometry and the understanding of the Earth shape. Heraclitus said: “There is nothing permanent except change” and I am going to follow his wisdom. Some people simply prefer to believe into immutable things, it is easy, and some other people dare to touch the immutable things from time to time - to be sure they are really immutable... This article has been facilitated by a multi-hour debate between people from two aforementioned categories; the discussion was about pros and cons of a couple of design patterns when the context of the pattern applicability changed.>>
