Building Monorepo gRPC Services with Bazel
summary
Bazel builds gRPC services across many languages in a single monorepo by treating protoc as a reproducible toolchain that downloads protoc releases instead of compiling protoc C from source, and by wiring generated artifacts into targets so changes to a .proto propagate immediately to all consumers. The workflow uses gazelle generates BUILD files to avoid manual editing, a write_source_files helper to sync generated code into source trees, and a logger example that proves language-crossing rebuilds work. Continuous delivery tooling and an aspect init repo scaffold are available.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:02Why Bazel for gRPC
- 3:52Manual code generation challenges
- 6:38Bazel for Protocol Buffers
- 8:21Trunk-based development
- 10:49Incremental builds
- 12:56Automating build files
- 14:19Generated code location
- 17:27Syncing generated code
- 18:50gRPC-Bazel-Protobuf issues
- 21:21Q&A
