I am a little bit disagree with Dennis about ESB being "an essential component of a SOA". I do not want to couple SOA with a tool, which ESB is today. However, I think, an ESB is quite convenient element of SOA implementation. Reading Dennis' message further, I guess, he shares the same understanding.
I also agree that with current WS-* standards, such a costly environment as ESB is practical mostly for the large enterprises to deal with WebServices. The question remains if middle size companies need messaging pipe and WebServices, is ESB still sufficient?
I also agree that with current WS-* standards, such a costly environment as ESB is practical mostly for the large enterprises to deal with WebServices. The question remains if middle size companies need messaging pipe and WebServices, is ESB still sufficient?
So, if you build your WebServices infrastructure by yourself and implement all WS- standards, is it really cheaper than to buy and maintain an ESB ?
I do not see any significant changes caused by
emerging WS- standards vs. ESB for SOA. ESB is NOT a SOA but convenient communication channel(s) structure. Moreover, I prefer to deal with a solution knowing it does not lack one of the standards because the development project was cut earlier that time. This is why I applaud BEA for taking isolated open-source solutions and tools under consistency and integrity control, yes, for money, that buy pieces in balanced complex. So, I would rather go with light-weighted versions of ESB than with a hand-crafted SOA communication channel(s).
- Michael Poulin
Java Architect
(SOA, J2EE, distributed computing)
Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
Hi all,
I'd like to find out how list members view the use of ESBs in SOA. Based
on what I've read and discussions I've had off list, I suspect a fair
number of people view an ESB as an essential component of a SOA.
In my own talks on the topic I tell people that ESBs are especially good
for bridging legacy applications to a SOA. Beyond this, they can
certainly add a lot of value in the monitoring and control area.
However, I think there's been way too much marketing hype from the
vendors that conflates ESBs with SOA. Especially now that WS-Addressing,
WS-ReliableMessaging, and WS-AtomicTransactio ns are becoming standard
components of the SOAP stacks (and WS-Eventing is getting closer), the
value added to Web services by an ESB seems to me to be minimal for all
but the largest enterprises.
The main drawback I see to using an ESB is that you're building your
enterprise around proprietary software. Even the open source ESBs all
have their own unique ways of configuring and managing services. The net
effect is that you're locked into a particular service bus and will find
it increasingly difficult to break free over time.
How do other people feel about this?
- Dennis
--
Dennis M. Sosnoski
SOA, Web Services, and XML
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail Beta. __._,_.___
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
