12 engineers on Hacker News describe using gRPC first-hand: 3 endorse it, 4 regret it, 0 are mixed.
“We replaced ROS with GRPC, foxglove and our own code. Works reliably, much better to handle. Would recommend everyone else to try it”
endorse · production · sashank_1509 · 2025-01-19 · source ↗ · wrong label?“I've seen trouble with gRPC and trying to debug it is infuriating.”
regret · production · inetknght · 2023-11-24 · source ↗ · wrong label?“My company uses gRPC and it's an absolute nightmare but not so much to the point where we'd use a company like this”
regret · production · tlackemann · 2021-12-09 · source ↗ · wrong label?“In both cases (gRPC and GraphQL) we've run into so many issues that the technology was abandoned and we fell back to plain JSON REST.”
regret · production · bcheung · 2018-10-24 · source ↗ · wrong label?“gRPC ensures that we have sane contracts between our services, making it easier to separate our offering into little modules.”
endorse · production · nevi-me · 2018-07-02 · source ↗ · wrong label?“Everything with gRPC. ... It'd be great to be able to use grpc across the whole stack.”
endorse · production · codesuki · 2018-05-29 · source ↗ · wrong label?“That hasn't been a problem until we tried to install google-api gem and found out grpc doesn't play well with muslc.”
regret · production · hosh · 2017-04-19 · source ↗ · wrong label?“I run several grpc apis written in rust in prod”
neutral · production · tuetuopay · 2024-12-17 · source ↗ · wrong label?“have everything mTLS'd together, and have all of DNS+cert + routing magic”
neutral · production · FridgeSeal · 2022-08-01 · source ↗ · wrong label?“No, we use Kubernetes, grpc and protobuf as base”
neutral · production · ivyabc · 2020-12-03 · source ↗ · wrong label?“since you had to use 'grpc' (e.g. stubby inside)”
neutral · production · 2.5 yr · malkia · 2019-01-07 · source ↗ · wrong label?“We use it together with gRPC to form our microservice stack”
neutral · production · mwitkow · 2016-12-13 · source ↗ · wrong label?