Binary serialization vs. JSON vs. xml [closed]

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 9 years ago.

Does anyone know what are approximately the performance gains, in terms of time, when using binary serialization versus JSON versus xml and sending the data over the network, provided that the data structures have a lot of small (string) fields?

To what extend is the serializer responsible for the performance? What about the programming language?

The perfect scenery is the one in which we ignore the portability problems and we assume we have at disposal the libraries needed for serializing/deserializing to and from all 3 formats.

Answer 1

It's kind of impossible to answer your question adequately, because it depends on your specific requirements and needs.

To some extend you could say it's the amount of data used to describe the serialized representation, which influences the performance.

For example, a XML document would need opening and closing tags like ..., while JSON would suffice with prop1:"...", which reduces the amount of character data needed to describe the instance. Binary might even skip the property naming, which then further reduces the amount of data needed to describe the serialized instance.

Although this might paint the picture binary serialization would be the fastest, it isn't always the case. It depends on how much time the serializer needs to get from an object instance to the serialized description.

If you really need performance, then you should take a look at the google protocol buffers. In my experience these are lightning fast and quite easy to use.