3 ms·
"Reason #3: Less Boilerplate Code" Anyone who has used Avro in Java knows that this is not true.
by don_draper 12y ago
"Reason #3: Less Boilerplate Code"
Anyone who has used Avro in Java knows that this is not true.
- nly 12y agoAvro code is generated though?
- don_draper 12y agoFor anything non trivial, putting data into an Avro object and pulling it out is manual and tedious. Instead of json_parse("{'nice json':'string'}) you have to assemble the object and for large hierarchical objects this is a pain. And then you want to return that object to the UI. Well it's not standard JSON. For example the arrays aren't simple arrays. My team has code to fix these kinds of things but it's not nearly as easy to use as JSON. tl;dr Avro JSON != Standard JSON The OP's assertions that the protocol buffer's are awesome and reduce boilerplate conflict with my experience.
- nly 12y agoI don't see how "standard JSON" could be any easier when it's even less structured.
- nostrademons 12y agoCurious what this has to do with protocol buffers?