Analysis of domestic data exchange platforms

The data exchange platform should be based on the infrastructure provided by the platform itself. Most of the exchange platform systems in China mistakenly focus on the transmission protocols supported by the data exchange platform (such as mq, ftp, webservice), the more transmission protocols the system supports, the more difficult it is for the system to abstract business logic. For the user, it does not care which transmission method the system uses and how to exchange data, it is often more willing to choose a simple, standardAnd the interface that does not destroy the original system structure, this is a kind of "data exchange that can be carried out with the least cost" interface. I have participated in the data exchange between a municipal garden bureau and a city government network center, their so-called data exchange platformIt is nothing more than some expansion in Web service technology, the system looks different, one is not like an authentic data exchange platform, and the other is not like an enterprise service bus (Enterprise Service Bus), then what is an authentic data exchange platform,Personally, I think it is a foreign Xware product. Xware defines many business document components. These components are built on many transmission protocols such as jms, mq and ftp. Why do you do this?The reason is that transmission protocols such as jms and mq have the ability to transmit messages. They can exchange messages without using the infrastructure of the data exchange platform. They are included to provide the ability to transmit messages.The only shortcoming is that each transmission has its own interface standard and transmission message protocol. The data exchange center should have its own message protocol, such as Xware's Document Xml and the national administrative service agency's electronic document exchange format Eapp Xml.Etc., the data exchange platform introduces the concept of "adapter" in order to support its own message protocol. The concept of an adapter is a component that connects one protocol to another protocol, that is, an adapter is used to coordinate the communication between the two protocols.The data exchange platform should not pay attention to the so-called many transmission protocols, and providing more does not necessarily bring any benefits, and often the harm outweighs the benefit.If you want to make a product of the nature of a data exchange platform competitive, you need to focus on the infrastructure of the platform, and what transport protocols are on top of, what is the infrastructure: in my opinion, in addition to these transport protocols can functionOther functions, such as webservice, can transmit messages, but cannot schedule transmission, electronically sign message data, and perform unified message management.If it is only for data exchange, it is recommended that you simply use web services. Don't tout the "universal" data exchange system for those systems that are simply extended on top of web services. This omnipotence does not depend on what you developed.How good the data exchange platform is, but thanks to the characteristics of the web service itself, so most of the domestic data exchange platforms are middleware for system integration rather than authentic data exchange platforms.