Software systems evolution, file commute protoc

in many locations have a This is quite similar to the an human to tell different thing.
one thing while a person should tell another person, we can along call, mail, SMS, IM tool or a course to communicate face to face that. This approach is similar to the system data exchange through tcp, udp, pipes,Womens Lacoste Trainers, etc. ways. When two human communicate, we need a common language to know each other's meaning, the same, the two systems to exchange data, yet too need to define a mutually understood protocol, we called the
Data exchange protocol
data exchange protocol is intended to correct the data the two systems interact. Therefore, almost all development languages ​​provide a convenient data exchange capabilities. For sample, using the JAVA language development system uses MySQL database to store data, through data exchange agreements with MySQL MySQL to do data exchange; via JAVA RMI can easily do the cross-machine distributed data exchange, RMI is a data exchange accession.
generally in different systems, exchange data among different languages, we will prefer the exchange agreement or a common elucidation of one simple to use their own exchange agreements. WebService once very renowned in the Web 2.0 epoch, lightweight REST protocol began to be sought behind. So what exactly is in our system should select what variety of agreement?
How to choose the data exchange protocol
choose what kind of agreement with our scenario of a magnificent relationship. We need to consider if we have amplified to assist the interface is easy to release, need to consider the cost of bandwidth, serialization and deserialization of the performance, scalability, and so the interface protocol. Here we see some of the more common exchange protocol. Agreement
Achieve
Cross-language
Performance
Traffic
RPC xml
Widely
Almost all
Low
Great
N (to effect) json
Widely
Large
General
General
N (to accomplish) php serialize
PHPRPC
Large
General
General
Y hessian
hessian
Large
General
Small
Y thrift
thrift
Large
High
Small
Y protobuf
protobuf
Large
High
Small
N (to achieve) ice
ice
Large
High
Small
Y avro
Apache Avro small
High
Small
Y messagepack
messagepack

Large
High
Small
Y
above table lists some common data exchange protocol fall butme of the features of the approximation. No extra nice or bad here, just ambition to show that different data exchange protocol is different, so we need in our scenarios to choose.
Open
like microblogging, SNS this open platform, providing static html page javascript interface to shriek the system are of this type. This type is represented by:
caller is not fully controllable,New Lacoste Trainers High Top, but also for the public network, you may not know who, what language, what is called your way to provide the data interface; Interface Visits are generally very large, requiring high performance and throughput; need to consider security issues, outer data submitted may not be legal.
so in this circumstance, the need to think the data transportation bandwidth consumption and ease of data exchange protocols, and multi-language support class. Html page ahead the javascript for the interfaces are generally invoked using the XML format,Lacoste Trainers, in recent annuals almost all rotated into json format, because the json vehicle namely smaller, easier to use than XML. As for the open platform, deserving to the use of scenarios, so it needs to provide a kind of exchange protocol format. Basically, ambition provide XML and json. In array to enhance the performance of the platform itself and the client's performance, tin provide such a binary protobuf exchange protocol support and amplify the compression to save bandwidth, transportation and expense of interpretative performance.
Internal Service
for a large system, the internal data exchange services everywhere. From the most basic and common data exchange database,Lacoste Swerve Keyline Trainers, memcached caching data exchange, data exchange message queue to the system used between the RPC service framework, etc., can be regarded as internal service data exchange. Is characterized by internal services without regard to the firewall, no opening up quick (almost no bandwidth prices).
internal service data exchange protocol choice is very great, generally need to consider:
the extravaganza of data interchange protocol to aid the absence for cross-language data exchange protocol message body size of the persistent storage
for persistent storage, each type of data exchange protocol can in fact be achieved. Generally need to consider scenarios:
whether man can read the series of storage space consumption and deserialization of ziped cross-language performance is
assume the front page of our Web site introduction wafer development using the PHP language,Lacoste Camden Trainers, intermediate business logic development using JAVA language, then it comes to cross-language data exchange problems. As long as the system is not simply the use of a language, then we must consider this publish. In truth, consider the hereafter expansion and needs alteration, it's best to consider the cross-language data exchange protocol.
Scalable data exchange protocol
in the choice of data exchange protocol, we also need to be considered similar to a database table? schema chart of the expansion problem. Provide consumer message such as a data exchange protocol interface now includes user name, gender, residence information, the upgrade process, added a final login IP information. If you do not consider the data exchange protocol to upgrade the shock is likely to guide to abnormal former consumer or the antique data can not correctly decide the problem.
Using compatible protocol
Using
compatible protocol is very serviceable to provide new products compatible with the existing mature data exchange protocols,Lacoste Protect Laser Trainers, can reduce the threshold for the use and speed of product development. Such as Sina on the use of open source memcacheQ memcached protocol.
Summary
variety of common data exchange protocol is very much open-source implementation, data exchange protocol is a very broad expression, in fact, at all times the comprehension of the data serialization and deserialization, then it can be said that an agreement to exchange data . Data exchange protocol performance is actually serialized and deserialized performance, if paired with RPC, then the performance itself with the RPC implementation has a very large relationship.