JSON Schema IS a thing (json-schema dot org), so it's not quite fair to say that there's NO support for schema validation. Protobuf is still always going to win on performance, of course. Especially since adding schema validation to JSON-based APIs only makes them even slower.
Thanks for the article NK, really interesting for people like me who didn't work with protocol buffers.
I'd highlight your section on rolling it out. It's easy to design theoretical architectures, another thing is rolling that out in existing services. Makes sense to implement an existing framework, upgrade version, and still have a feature toggle to release in a controlled manner.
JSON -> Binary, yea totally makes sense for perf wins.
Great read, thanks. What would you classify as a big payload?
Thanks for the mention NK! I love your newsletter as well.
Thanks NK for the detailed explanations. Why does JS doesn’t perform as good as Java or python using Protobuf?
JSON Schema IS a thing (json-schema dot org), so it's not quite fair to say that there's NO support for schema validation. Protobuf is still always going to win on performance, of course. Especially since adding schema validation to JSON-based APIs only makes them even slower.
Thanks for the article NK, really interesting for people like me who didn't work with protocol buffers.
I'd highlight your section on rolling it out. It's easy to design theoretical architectures, another thing is rolling that out in existing services. Makes sense to implement an existing framework, upgrade version, and still have a feature toggle to release in a controlled manner.
Really enjoyed the article and the analogy at the beginning. Thanks, NK