gRPC
No written verdict yet. Here is what commenters said.
Why people recommend it
“I've only enjoyed using Protobuf + gRPC after we've started using https://buf.build.”
“gRPC forces you to confront them early and explicitly IMO, which is not a bad thing.”
Show 2 more
“I like implementing this standard gRPC interface”
“I think gRPC and using it with json is awesome”
Caveats and dissent
“it's still a nightmare trying to integrate with gRPC from something remotely modern”
“it doesn't, instead it needs to run inside mings”
Show 2 more
“an issue with gRPC which results in thousands of connections and constant connection churn”
“You're right about the gRPC fidelity issues though.”
Often compared with
Who recommends it in their own words
Threads where it came up
- gRPC: From service definition to wire format 3 mentions
- Transfering Files with gRPC 3 mentions
- One Interface, Every Protocol 2 mentions
- Ask HN: Who wants to be hired? (February 2026) 2 mentions
- The Agent SDK 1 mention
- How Uber Protects Against Retry Storms 1 mention
Data: grpc.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 27
“Mainly gRPC for cross-service communication”
“In gRPC, the statuses it returns in trailers can include arbitrary details”
“it's still a nightmare trying to integrate with gRPC from something remotely modern”
“client-streaming gRPC”
“it doesn't, instead it needs to run inside mings”
“not yet supported by gRPC”
“microservices price tracker with Kafka and gRPC”
“an issue with gRPC which results in thousands of connections and constant connection churn”
My gRPC point is that it already gives you a language for describing interfaces and support for generating client types from it, and already abstracts the connection management[1]. If OBI just generated a gRPC ClientConn implementation to map the Invoke calls to eg REST paths, it’d inherit the large existing gRPC client ecosystem. That ClientConn interface can already technically capture what OBI calls binding execut
“You're right about the gRPC fidelity issues though.”
“Whether it’s Pusher, Pub/Sub, or even high-tuned gRPC, the 'Serialization Tax' always wins.”
“Rust web+gRPC server”
“servers can send SERVING/NOT_SERVING signals proactively when they want to drain”
“gRPC's xDS client is not always bugs-free”
“I've only enjoyed using Protobuf + gRPC after we've started using https://buf.build.”
“it can interoperate with normal grpc servers”
“with Kubernetes, gRPC, Prometheus/Grafana, PostgreSQL/Redis, and Terraform”
“gRPC”
“gRPC/HTTP/Kafka/WebSocket”
“gRPC forces you to confront them early and explicitly IMO, which is not a bad thing.”
“Having protobufs for that was genuinely useful. But trying to pipe multi-gigabyte files through gRPC streams was painful.”
“I like implementing this standard gRPC interface”
“I think gRPC and using it with json is awesome”
“comes with bloat, is a bit of a mess in Python”
“networks wasm components using gRPC”
On this “types first across languages”, I’ve been hacking on something in that vein called Kumi (typed calculation schemas compiled to Ruby/JS). Tiny demo here https://kumi-play-web.fly.dev
“Tech stack: Go, gRPC, KurrentDB”