毕业设计外文文献—开源ESB的世界.docxVIP

附录A 外文翻译—原文部分 The World Of Open Source ESBs By:Tijs Rademakers、Jos Dirksen Source:《Open-Source ESBs in Action》 1.1 Why do you need an ESB? A lot of the early ESB products had a history in the enterprise application integra-tion market. It was sometimes hard to tell the difference between some ESB products and their EAI predecessors! However, we can identify two main differences between EAI and ESB products. The first is the change from the hub-and-spoke model in EAI products to a bus-based model in ESB products. The hub-and-spoke model is a centralized architecture, where all data exchange is processed by a hub, or broker. The hub-and-spoke model can be seen as the successor of the point-to-point model. The bus model, on the other hand, uses a distributed architecture, in which the ESB functionality can be implemented by several physically separated functions. A second main difference between EAI and ESB products is the use of open stan-dards. EAI products like WebSphere Message Broker, TIBCO BusinessWorks, and Sonic XQ were mainly based on proprietary technology to implement messaging func-tionality and transformation logic. ESB products are based on open standards, such as Java Message Service (JMS), XML, J2EE Connector Architecture (JCA), and web ser-vices standards. As we mentioned earlier, many current ESB products have a background in the EAI space. So newer versions of WebSphere Message Broker (version 6), TIBCO Business-Works (version 5), and Sonic ESB (yes, the name has changed) are now marketed as ESBs but still have a strong foundation in EAI. In addition, a number of ESBs have been built from the ground up, like WebSphere ESB, Cordys, and TIBCO ActiveMatrix Service Grid. Because open source ESBs were not yet available during the EAI period, they don’t have a history in the implementation of proprietary technology. Many integra-tion specifications like JMS and Java Business Integration (JBI) are available, and open source ESBs use these specifications as