集成技术比较与选择 Comparison and selection of integration technology

CORBA和Web服务技术是当前解决分布、异构问题的最重要的代表，采用CORBA和采用Web服务都可以进行应用集成。
CORBA and Web service are the most important technology to solve current distributive, heterogeneous problems, integration applies CORBA and Web service to integrate.
但是，采用CORBA集成这些的系统有一个共同的缺陷，就是它们要求服务客户端与系统提供的服务本身之间必须进行紧密祸合，即要求一个同类基本结构。这样的系统往往十分脆弱：如果一端的执行机制发生变化，那么另一端便会崩溃。例如，如果服务器应用程序的接口发生更改，那么客户端便会崩溃。
But there is a defect in integration system with CORBA, it need a homogeneous basic structure connected with service client and system tightly.Such a system is very fragile: the other side is collapsed if one side execution system changes.For example, if interface of server application changes, client will collapse.
要求提供紧密耦合的基本结构，无可厚非，许多应用程序均是基于这种系统构建而成的。但是，对于电子商务环境下的供应链管理而言，供应链节点企业间经常会增加新的应用，或者对电子商务的流程进行更改，或者应合作伙伴的需求对应用进行更改。在这种情况下，便很难实现单一而统一的基本结构。你根本无法保证你希望与之进行远程通信的管道的另一端，具备所有你需要的基本结构：对于它使用的操作系统、对象模型或编程语言，你可能一无所知。
Many systems are constructed in such kind of system connected tightly.But for supply chain management in E-commerce environment, enterprises in supply chain nodes always increase new application, or change the E-commerce process, or modify the application to meet cooperation partners need.It is hard to implement single, unified basic structure in such condition. You cannot assure the other side remote communication channel with the basic structure as you need: you may know nothing about the OS, object model or programming language it applied.

华译网北京翻译公司翻译过大量有关集成技术比较与选择的文件资料,Beijing Chinese Translation Service Company has translated many technical documents about Comparison and selection of integration technology
相反，Web服务彼此是松散偶合的。连接中的任何一方均可更改执行机制，却不影响应用程序的正常运行。从技术角度讲，人们己转向使用一种基于消息的异步技术来实现高可靠性的系统性能，通过使用诸如HTTP、XML等来实现统一的连接。
Reversely, Web service is loosely coupled each other.Any side in connection can change execution system without affecting normal application performance.In technical view, people turn to apply a message-based asynchronization technology to perform high reliable system performance through unified connection by HTTP, XML etc.
消息传递系统将通信的基本单元打包成自我描述型的数据包（又称作消息），并将其放到网络缆线中。消息传递系统与分布式对象系统之间的本质区别在于：要求发送方辨识接收方的基本结构的程度有所不同。在分布式系统中，发送方需对接收方的情况做出种种猜测：应用程序是如何激活或拆包的，调用的是什么样的界面，等等。
Message transfer system packages basic unit of communication as self-descriptive data package (called message) and put it in the network cable. The basic difference between message transfer system and distributive object system is: the difference of basic structure level sender identified receiver. In the distributive system, sender need assume the condition of receiver: application activation or disassembling, interface invoking etc.
另一方面，消息传递系统会在缆线格式级上创建合同。发送方既不需考虑消息被接收后的情况，也不需考虑接发双方之间的通信情况，唯一需要考虑的是接收方是否能辨识发送的消息内容。
On the other side, message transfer system creates contract at cable format level.The sender does not need neither the received condition nor the communication condition between two parties, the only thing to consider is whether receiver identifies the message content or not.
在缆线格式级上创建合同的优势不言而喻。例如，接收方可在任何时刻进行更改，而不会干扰发送方的消息发送，只要它仍可辨识原有消息的内容。另外，发送方无需任何特殊的软件即可与接收方通信：只要它发出正确格式的消息，接收方就可以响应。
The advantage of contract on cable format level is obvious. For example, receiver can change at any moment without interference to sender’s message, if only it recognizes the original message.In addition, sender need not any particular software to communicate with receiver: receiver responses if only the message format is correct.
Web服务改变了COBRA集成复杂系统对接的实现方法。然而，要求企业抛弃现存的应用集成底层架构，并且盲目地转向开发基于Web服务的解决方案来替代它是不太现实的。在使用Web服务的场所，不是替代（至少现在还不是），而是应该使用Web服务来支撑现存的下层结构。[8][9]
Web service changes the method of docking of complex system COBRA integrated. However, it is not realistic to require enterprises abandoning existing application architecture and developing Web service based solution to replace blindly.In some place applied Web service, not replace at least, it applies Web service to support existing underlayer structure.[8][9]