On a previous episode of Go Time we discussed binary bloat, and how the Go protocol buffer implementation is a big offender. In this episode we dive into the history of protocol buffers and gRPC, then we discuss how the protocol and the implementation can vary and lead to things like binary bloat.

Join the discussion

Changelog++ members save 4 minutes on this episode because they made the ads disappear. Join today!

Sponsors:

• Square – Develop on the platform that sellers trust. There is a massive opportunity for developers to support Square sellers by building apps for today’s business needs. Learn more at changelog.com/square to dive into the docs, APIs, SDKs and to create your Square Developer account — tell them Changelog sent you.
• FireHydrant – The reliability platform for every developer. Incidents impact everyone, not just SREs. FireHydrant gives teams the tools to maintain service catalogs, respond to incidents, communicate through status pages, and learn with retrospectives. Small teams up to 10 people can get started for free with all FireHydrant features included. No credit card required to sign up. Learn more at firehydrant.com/
• Calhoun Black Friday – Go Time co-host Jon Calhoun is having a Black Friday sale on November 21st-29th. All paid courses will be 50% OFF. Learn more about Jon’s courses at calhoun.io/courses

Featuring:

• Akshay Shah – Twitter, GitHub, LinkedIn, Website
• Jon Calhoun – Twitter, GitHub, Website
• Johnny Boursiquot – Twitter, GitHub, Website

Show Notes:

• Where Akshay works
• Buf’s gRPC implementation
• bufbuild/connect-go
• bufbuild/connect-web
• Google’s Protocol Buffers overview
• gRPC docs
• Google’s grpc-go
• gRPC benchmarks
• HTTP2.md">gRPC spec
• hand-write a gRPC handler in 7m

Something missing or broken? time-256.md">PRs welcome!