Protocol Buffers- A Banked Journey
summary
Banked defines shared error and message schemas once using proto3 and generates Go/TypeScript/Ruby types with protoc + protoc-gen-go until switching to buf.build for linting, breaking-change checks, dependency locking and remote codegen. CI runs buf, commits generated code back to the PR, and enforces V1 package layout. protogen-validate enforces rules (UUIDs), events go out to NATS JetStream as JSON envelopes for data consumers, and work toward grpc Gateway and full gRPC is underway; the workflow reduces drift and works in practice.
AI-written summary · about
chapters (16)
- 0:00Start
- 4:49What Is What Is Protocol Buffers
- 5:37What a Protocol Buffer File Looks like from Top to Bottom
- 8:50Field Types
- 9:17Packet Structure
- 11:48Demos
- 18:39Restructuring the Proto-C Packages
- 22:23Compatibility Checks
- 28:07The Braking Change Detection
- 28:18Breaking Chain Generation
- 29:23Manage Mode
- 32:25Remote Code Generation
- 37:17Github Action
- 38:51Github Actions Code
- 44:16Package Organization and Usage of the Schema Registry
- 44:58Could We Use Protocol Buffers for Our Public Apis
related talks
21mManaging Protocol Buffers at Scale
35mProtocol Buffers for FHIR
37mProtobuf and buf: glamour, misery, and import substitution
13mFrom Writing REST to Writing gRPC
35mShow Me the Schema! RPCs and Learning to Love Code Gen
23mEffective Protobuf: Everything You Wanted To Know, But Never Dared To Ask
07mGRPC & Go
20mUnifying gRPC APIs under One Roof: Mastering gRPC Federation for Efficient BFFs