> OK, I think I am reading a suggestion that an ESB is essentially
> something that can integrate the flow of information across multiple
> transfer mechanisms, some of which use standard protocols, some of
> which use language-specific APIs, some may be more proprietary than
> that. I can go with that, with the addition that there is some
> development and runtime management as well.
I like to use the term "vendor neutralization". Anything that you utilize in
your SOA to manage the impact of multiple interfaces, to me, is an ESB. The ESB
conveys data between entities in a way that is convenient for your
architecture/business needs.
Gregg Wonderly
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.
