This was a good read; I'm mainly Go now, but simpler Protobuf in Java is something that I'd love to see. I sent you a small PR (https://github.com/myfear/ejq_substack_articles/pull/8) that adds Protovalidate support.
Will do! I'm working through a holiday backlog right now, so I'll aim for next week. I'll follow your format: intro, bootstrapping, and a walkthrough of the diff from base state.
Solid tutorial with practical tradeoffs laid out clearly. The 60% payload reduction is meaningul in high-throughput scenarios, but what stood out was keeping the existing REST architecture intact rather than forcing a full gRPC migration. I've used a similar setup on microservices where mobile clients needed smaller payloads but debugging still required readable JSON endpoints. The reserved field number tip is crucial - saw that bite a team once when someone reused field 5 and broke backward compatibilty across versions.
This was a good read; I'm mainly Go now, but simpler Protobuf in Java is something that I'd love to see. I sent you a small PR (https://github.com/myfear/ejq_substack_articles/pull/8) that adds Protovalidate support.
Thanks Joe! I’d absolutely would love to see this explored in a follow up post! Wanna drop me a draft via email and l I’ll get it scheduled?
Will do! I'm working through a holiday backlog right now, so I'll aim for next week. I'll follow your format: intro, bootstrapping, and a walkthrough of the diff from base state.
Solid tutorial with practical tradeoffs laid out clearly. The 60% payload reduction is meaningul in high-throughput scenarios, but what stood out was keeping the existing REST architecture intact rather than forcing a full gRPC migration. I've used a similar setup on microservices where mobile clients needed smaller payloads but debugging still required readable JSON endpoints. The reserved field number tip is crucial - saw that bite a team once when someone reused field 5 and broke backward compatibilty across versions.