I would like to know the merits & de-merits of
I want to implement one common framework for two application, one in Perl and second in Java. So, would like to create common service which can be used by both technology i.e. Perl & Java.
Both are web-applications.
Please share me your valuable thoughts & suggestion on this. I have seen many links on google but all have mixed opinions.
Protobuf is mostly useful for internal services whereas JSON is mostly useful for web applications. Prior knowledge of schema is essential in decoding Protobuf messages, whereas data can be easily decoded or parsed in JSON with knowing schemas in advance.
It is essential to be aware that protobuf is not necessarily the fastest option. If your data is mainly string, then JSON format might be a good choice.
Utility classes to convert protobuf messages to/from JSON format. The JSON format follows Proto3 JSON specification and only proto3 features are supported.
Protobuf messages were 9% smaller than JSON messages and they took only 4% less time to be available to the JavaScript code.
Json
XML
Protobuf
All have good support on most platforms.
Personally, I rarely use XML these days. If the consumer is a browser or a public API I tend to use json. For internal APIs I tend to use protobuf for performance. Offering both on public API (either via headers, or separate endpoints) works well too.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With