Why Does gRPC Configure Clients with JSON?
gRPC's service config controls load balancing, retries, and timeouts, and in grpc-go you write it as a raw JSON string. Here's why, and why it shouldn't still be the only option.
gRPC's service config controls load balancing, retries, and timeouts, and in grpc-go you write it as a raw JSON string. Here's why, and why it shouldn't still be the only option.
Agents write more of the code now, but systems still have to fit together properly. Protobuf contracts and Buf checks keep APIs aligned and standardized.
Why Buf builds first-class Protobuf and Connect libraries for TypeScript and Python instead of patching the upstream runtimes.
A protoc plugin that turns Jev questions in a .proto file into typed Go, TypeScript, and Python clients.
The traditional advice is REST for public APIs and gRPC for microservices. But is this a false dichotomy? (hint: yes)
Learn how to generate JSON Schema and OpenAPI specs using Protobuf.
Deep dive into a space-saving encoding technique.
Why gRPC-Web made the browser a second-class client, the protocol compromises that followed, and what a web-native RPC protocol looks like instead.
Anthropic built connect-rust and has contributed it to the Connect project. Rust now has an official implementation that speaks Connect, gRPC, and gRPC-Web.
A tour of the modern Protobuf workflow, from compatibility and code generation to RPC, validation, and editor tooling, and how each piece builds on the same schema.