tag:blogger.com,1999:blog-2002573816058150704.post7428682003818437582..comments2007-12-09T22:04:29.076ZGuy Sayarhttp://www.blogger.com/profile/12117735865517101079noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2002573816058150704.post-39130645841772593582007-12-09T22:04:00.000Z2007-12-09T22:04:00.000ZWell, an ESB like SOA is an abstract concept.<BR/>ESB does not implement a service-oriented architecture but provides the features with which one may be implemented.<BR/>It tries to decouple the services from the actual transport layer, like in EAI. Using Web Services as I see it, breaks the idea of an ESB, as it couples all services by forcing this API as the interoperability layer.<BR/>a proper ESB should support a variety of protocols to enable the transition and decoupling of different systems/services and languages.<BR/><BR/>In Enterprise organizations that are having hundreds of interfaces and systems the ESB is a valuable entity (together with the implementation of SOA). implementing an ESB will give them the visibility and reuse they are seeking together with the means to force security and permission policy.<BR/><BR/>In the efficient low latency world an ESB might impact performance, and is quite a "white elephant" as the benefit from reuse, decoupling and visibility are usually a second priority to performance, and is archived by OO design together with visual monitoring tools.Mickeynoreply@blogger.comtag:blogger.com,1999:blog-2002573816058150704.post-91204680767040947282007-11-15T18:04:00.000Z2007-11-15T18:04:00.000ZVery Good post, I like the clarity of the explanation.nirpazhttp://www.blogger.com/profile/16110455243678144584noreply@blogger.com