Gervas Douglas wrote:
> <<As someone who has been steeped in Service-Oriented Architecture
> (SOA) for years, I freely admit to thinking, only occasionally, of
> course, "Why would anyone want an Enterprise Service Bus (ESB)?" On
> the other hand, there's no lack of quotes and articles written by ESB
> infrastructure vendors claiming there's no need for dedicated SOA
> infrastructure, since ESB infrastructure does everything a company
> could possibly need and more. Of course, I know I'm right—just as the
> ESB vendors know they are right. As someone with no vested interest in
> either, I imagine you're both confused and amused—but mostly confused.
The power of an ESB thingy is that it provides the neutralization or
standardization layer away from every application. I.e. if you don't
neutralize, and instead provide multiple implementation support in each client
interface, that doesn't scale well. An ESB thingy lets you neuralize at a
central point which allows you to do it once. It also allows you to refocus on
a different interface implementation in one place as well as recombine disjoint
data into a new package.
Gregg Wonderly
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
