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-AtomicTransactions 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 ------------------------ Yahoo! Groups Sponsor --------------------~--> See what's inside the new Yahoo! Groups email. http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> 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/
