Re:The rise and rise of JSON (2017)
by denormalfloat on Friday August 24, 2018 @03:35AM
(#17833400)
What shared contracts are there for JSON? The only one I know of is OpenAPI/Swagger, and that's already complicated. Wireshark is used because sometimes we don't have the source code for software we use. The only way to debug is to see what's on the wire.
I would argue that the fact that json doesn't have schema support built in makes it more difficult to handle those issues though.
Re:The rise and rise of JSON (2017)
by humbleMouse on Friday August 24, 2018 @02:57AM
(#17833258)
Avro json schemas and jackson json annotation for POJOS makes json object schemas easy to implement. Versioned object repos make great shared schemas and are easier to manage than xsds. (imo)
Anything would be better than XSD (though I don't think JVM-only is a good idea), but with an object you still don't necessarily know what kind of changes are going to be forward compatible or not. The only thing I've had any success with is something like Thrift or Protocol Buffers, where the canonical definition of your objects is a terse, Algol-like syntax but one that's been designed explicitly with version compatibility in mind, and you know exactly what changes do or don't break compatibility.
Your other complaints stem from poor system design and lack of shared data contracts. They could be complaints about any data format.