2 ms·
"There are plenty of well-established binary protocols that are both easy to parse and use little memory, e.g. Protocol buffers, Avro or Thrift." I'd just like
by mcguire 11y ago
"There are plenty of well-established binary protocols that are both easy to parse and use little memory, e.g. Protocol buffers, Avro or Thrift."
I'd just like to point out that none of JSON, Protocol Buffers, Avro, or Thrift are protocols. They're serialization/unserialization formats/libraries/frameworks of greater or lesser tonnage. Whether they suck or not largely depends on how they're used; if you're tunnelling all of your communications over HTTP, you might want to do something HTTP-friendly.
"Not to mention Swagger, the de facto standard for REST documentation, officially claims such approach is "not per design" - and sticks to fixed URIs."
What? (One of the great downsides of REST is that most of the tools that claim to support RESTful designs, including JSR311 and apparently Swagger (I've never used it) simply don't.)