Comparison of several communication protocols

2008-09-20 00:07
A review
This story compares the RMI, Hessian, Burlap, Httpinvoker, web service, 5 kinds of communication protocols in differ data and different data structures when transmission performance.
RMI java language itself is a remote communication protocol, settled and efficient, is the foundation for the EJB. But it can merely be used for communication among the JAVA program.
Hessian and Burlap namely caucho invested along open source protocol,Kids' Supra TK Society, HTTP-based transport, the waiter do not open the firewall ports. Protocol specification public, can be secondhand in any language.
Httpinvoker is SpringFramework provide remote communication protocol, can only be used for communication between JAVA program, and the server and the customer must use SpringFramework.
Web service is apt join heterogeneous systems alternatively heterogeneous language accepted protocol, it uses SOAP form of communication, can be used in any language, many of the current evolution tools as their advocate is too quite nice.

test results show the efficiency of several communication protocols were:
RMI> Httpinvoker> = Hessian>> Burlap>> web service
RMI is indeed the choice of JAVA remoting protocol, very high permanence, primarily in the case of a crowd of of data, and additional communication protocols gap is particularly 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 time flat.
Hessian small objects in the transmission, but also quickly 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 transfer a data rate is acceptable, routinely, 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 that virtually not procedures spent time logging all the time are remote calls consuming.
2, RMI call
with the same mind, 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, different 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: 2 flat, Spring provides the service also slightly faster.
preliminary outlook is that this is because Spring's proxy and caching mechanism is relatively muscular,Women's Supra TK Society, save the object anew to get the time.
3, Hessian call
caucho resin server enterprise is understood as the fastest server in the java field have a definite reputation. Hessian for a resin makeup, its devise is very streamlined and efficient, the tangible operation has certified this point. On average, Hessian slower than about 20% of RMI, but only in particularly large amount of data, data structures are complex cases can be reflected, medium or small amount of data, Hessian is not slower than RMI.
Hessian has the advantage of streamlined, along languages ​​and protocol specification public, we can develop in any language for the implementation of their agreement. At present,Supra Indy NS Shoes, implementation language: java, c + +,. Net, python,Supra TK Society Shoes, ruby. No delphi implementation.
appending, Hessian and the WEB server with very good, with the maturity of WEB server functionality in handling large number of consumers have concurrent access to magnificent vantage in resource allocation, thread queues, exception handling, etc. can be composed of adult WEB server guarantees. The RMI does not provide multi-threaded server. Moreover, RMI need 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 building is not complex, middle measure of data in the case, the efficiency is still acceptable, merely if massive volumes of data, the efficiency would drop dramatically. On average, Burlap, RMI call while the coin 3 periods.
In my attitude, the cheap efficiency of two reasons, one is the portrayal of the contents of the XML data also, the same data structure, its traffic should be many larger; the other hand, we all know, 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 method call,Supra Muska Skytop Shoes, use the java object serialization mechanism to handle the convey. From the test results, its efficiency is still feasible, with the RMI smooth.
However, it can only be used for communication between the JAVA language, and that requires either client and server use the SPRING structure.
addition, HttpInvoker did not undergo the test of train, the current applying of the agreement have anyhow to ascertain the items.
6, web service call
The test chose 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 store object is instantiated only once. However, test results, web service efficiency or other communication protocols than 10 times slower.
If more than one reference point to take into list the transmission of the same object, web service to delay back more. As RMI, Hessian and other protocols can pass a reference, while the number of web service reference, how many objects should duplicate the entities.
Web service is the displacement of needless message over 1 of the reasons for its slow, monitoring found that the same access request,Supra Skytop III Shoes, depict 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 lofty xml parser to handle xml bean is cents resources. From the test results, remote calls faster than regional calls, but also from the side of the coin, the chief encoding and decoding used in the xml file. This is more serious than redundant information, redundant information is only occupied by web bandwidth and resources consumed in every call to the server instantly affect the load capability. (MS engineers have said, with WEB SERVICE can not load more than 100 concurrent users.)
Testing also base that, web service code not handy for non-basic types absence to enroll apart serialized and deserialized class, a lot of trouble, produce the stub is extra weary than spring + RMI / hessian uncomplicated process so smooth. Moreover, web service does not support set types, can only use orders, convenient