Women in Technology

Hear us Roar



Article:
  Using the ESB Service Container
Subject:   Multiple ESBs (pros and cons)
Date:   2006-02-13 08:36:30
From:   JeremyD
Dave,


I couldn't find a discussion thread for this topic so I figured I'd post this here.


What do you think are the pro's and con's of having an architectural strategy that supports multiple ESB's from multiple vendors?


In your book you mention point to point integration between multiple ESBs, but don't talk about whether the ESBs come from the same vendor or different vendors. (I realize ESB isn't a product one can purchase from a vendor)


Some U.S. agencies are turfy organization, and they seem to fear that if they don't own the bus, they are somehow not in control anymore.


Of course, the software vendors say their ESB's are compatible with other ESB's.


Some of the disadvantages that come to mind if different departments choose different ESBs for their infrastructure, are obvious:
Use of different development tools,
Management of upgrades, patches to multiple ESBs
Management of services themselves in different ESBs requiring staff trained in managing multiple tools
Interoperability between ESBs (even if each ESB claims to support all the standards)
High Cost - i.e. Licenses, Consulting and Operations
Incremental Deployment Supports
More technical issues due to the complexity of Data Sharing Architecture and ESBs interoperability


Are there other advantages/disadvantages for the federal government?


- Jeremy

Full Threads Oldest First

Showing messages 1 through 1 of 1.

  • Multiple ESBs (pros and cons)
    2007-12-09 07:28:59  mikegeorge12 [View]

    JeremyD,

    You may want to look at Java Business Integration (JBI) and its promise to bring standardization for integration components across ESBs. The forthcoming book on "Service Oriented Java Business Integration" by Binildas seems to provide details in this direction: http://www.packtpub.com/service-oriented-java-business-integration/book

    Mike