why is it said that remoting is faster than web services? Why XMLserializer is slow?

Question

Is remoting faster than web service or vice versa.

Also on what parameters can we differentiate the performance.

web service uses XMLserializer while Remoting uses binary

is xmlserialization a slow process and if yes than why?

Answer 1

is it faster because the size of the binary serialized object is smaller then the same object as an XML representation. And the time needed to transmit it across the wire is shorter

Answer 2

By "remoting" I assume you mean RPC/RMI calls.

Yes, comparing one RPC/RMI call to one web service call, then the RPC/RMI one typically comes out favorable in speed (binary is more compact, faster to encode and decode). But the largest time is typically spent on network latency, waiting for the messages to come across.

So in a realistic large complex system, the best choice is the one that minimizes the number of network requests. This has much to do with how language binding and remote service api looks.

The majority of RPC/RMI APIs I have seen promotes lots of remote calls, i.e. first you get the remote object, then you call a few setters leading to remote calls, then you ask the remote object to do something.

Web services are typically based on creating a large "document object" locally, and sending it over in one go. Requiring only one request-response.

Answer 3

by definition a web service is a stateless process, every time you request data the web service doesn't know what happened last. When you are doing remoting you are using the objects as they would have been locally so there is less overhead.