Stephen Patten - 17 - Jan 16, 2015


I’m wondering what would be a driving force for someone to adopt using the proto-buf binary serialization format in their web services? If I’m using JSON right now and it’s working fine, is there a compelling reason to switch?

 Thanks team! 

The drawback is that you have to add numeric indexes on each property (in which case MsgPack might be preferred), but otherwise it’s fast and compact and good for transferring binary data since it doesn’t need to be encoded. But in general unless given a reason not to I prefer JSON which is fast enough, self-describing and easier to debug.

You would consider ProtoBuf for larger payloads or where you’ve identified a hotspot bottleneck and you want better performance or smaller payloads.