Comparison of several communication protocols

2008-09-20 00:07
A review
This treatise compares the RMI, Hessian, Burlap, Httpinvoker, network service,Lacoste Tourelle Trainers, 5 varieties of communication protocols in another data and another data architectures when displacement representation.
RMI java language itself is a remote communication protocol, settled and effective, is the basis for the EJB. But it can only be used for communication among the JAVA program.
Hessian and Burlap is caucho provided by open source protocol, HTTP-based transport, the server do not open the firewall ports. Protocol specification public, can be used in any language.
Httpinvoker is SpringFramework provide remote communication protocol, can only be used for communication between JAVA program, and the server and the client have to use SpringFramework.
Web service is to join heterogeneous systems or heterogeneous language preferred protocol, it uses SOAP form of communication, can be used in any language, many of the current development tools for their support is also very good.

test results show the efficiency of several communication protocols were:
RMI> Httpinvoker> = Hessian>> Burlap>> web service
RMI namely indeed the alternative of JAVA remoting protocol, very lofty permanence, primarily in the circumstance of a crowd of of file, and other communication protocols gap is especially manifest.
HttpInvoker using java object serialization technology transfer, and RMI is essentially the same. From one efficiency point of view, the two are almost the same, HttpInvoker with RMI's transmissiin due time flat.
Hessian small objects in the transmission, but also hasty and efficient than the RMI, but the complex structure of data transfer objects or large amounts of data objects, RMI slower than about 20%.
Burlap only transmit a data rate is acceptable, commonly, it's coin three times when RMI.
Web Service inefficiency is well known, above average, Web Service communication cents to 10 times when the RMI.


Second, the results
1, a direct call
direct call when they all close to 0 mm, indicating namely virtually no procedures spent period logging all the time are remote calls consuming.
2, RMI call
with the same idea, RMI lesson is the fastest in almost all cases, the coin when it is fewest. Especially in complex data structures, large volumes of data in the case, the gap with other protocols is particularly evident.
To aggrandize the performance of RMI, distinct class to do the test, do not use Spring, use the original form of RMI (inherited UnicastRemoteObject object) to provide services and remote calls, and Spring's POJO RMI for efficient packaging into the approximation. The results showed: two flat, Spring provides the service also slightly faster.
preliminary outlook is that this is because Spring's surrogate and caching mechanism is relatively lusty, save the object anew to obtain the time.
3,Buy Lacoste Trainers, Hessian call
caucho resin server corporation is known as the fastest server in the java field have a certain dignity. Hessian as a resin makeup, its devise is very streamlined and efficient, the tangible operation has proved this point. On average, Hessian slower than approximately 20% of RMI, but only in particularly large measure of data, data structures are complex cases can be reflected, middling or small value of data, Hessian is not slower than RMI.
Hessian has the advantage of streamlined,Lacoste, across languages ​​and protocol description public, we can develop in anyone language for the implementation of their accord. At present, implementation language: java, c + +,. Net, python, ruby. No delphi implementation.
addition, Hessian and the WEB server with very good, with the maturity of WEB server functionality in treatment large digit of users have concurrent way to great advantage in resource allocation, thread queues, exception handling, etc. can be composed of mature WEB server guarantees. The RMI does not provide multi-threaded server. Moreover, RMI absence to open firewall ports, Hessian not.
4, Burlap and Hessian are called
Burlap caucho's open-source production, but Hessian binary path, and Burlap using xml format.
test results, Burlap in the data structure is not complex, medium amount of data in the case, the efficiency is still befitting, but if large volumes of data, the efficiency would drip dramatically. On average, Burlap, RMI call when the coin 3 times.
In my attitude, the low efficiency of two causes, one is the portrayal of the contents of the XML data also,Womens Lacoste Shua Trainers, the same data structure, its traffic should be much larger; the other hand,Lacoste Canvas Trainers, we all know,Lacoste Tennis Trainers, the xml parsing is more cost resources , especially for the case of especially large amount of data.
5, HttpInvoker call
HttpInvoker is SpringFramework provides JAVA remote means call, use the java object serialization mechanism to handle the transfer. From the test results, its efficiency is still possible, with the RMI smooth.
However, it can only be used for communication between the JAVA language, and that requires both client and server use the SPRING framework.
addition, HttpInvoker did not undergo the test of practice, the current petition of the agreement have additionally to ascertain the items.
6, web service call
The test selected components of the apache AXIS implementation as WEB SERVICE, AXIS WEB SERVICE field in the relatively mature veteran.
to only test data and encoding and decoding time, the client and server use the storage object is instantiated only once. However, test results, web service efficiency or other communication protocols than 10 times slower.
If more than 1 reference point to take into account the transmission of the same thing, web service to lag after more. As RMI, Hessian and other protocols can pass a reference, meantime the number of web service reference, how numerous objects ought duplicate the entities.
Web service is the transmission of redundant information over one of the reasons for its slow, monitoring found that the same access apply, describe the same data, web service returns the amount of data is the hessian protocol 6.5 times. In addition, WEB SERVICE are also coin processing, the current efficiency is generally not high xml parser to handle xml bean is pence resources. From the test results, remote calls faster than regional calls, but also from the side of the coin, the cardinal encoding and decoding used in the xml file. This is extra serious than redundant information, needless information is only occupied at network bandwidth and resources expended in every call apt the waiter directly influence the load capability. (MS engineers have said, with WEB SERVICE can not load more than 100 simultaneous consumers.)
Testing also base that, web service code not handy for non-basic types need to register apart serialized and deserialized class, a lot of difficulty, generate the stub is more exhausted than spring + RMI / hessian simple process so flat. Moreover, web service does not patronize set types, can only use orders, convenient