A middle ground that worked for us: gRPC between backend services, plus a thin REST/JSON gateway at the edge for browsers and third parties. Protobuf is still the single source of truth.
REST OR GRPC BETWEEN THREE SERVICES AND A MOBILE APP? OUR FOUR-PERSON TEAM IS SPLIT DOWN THE MIDDLE
@tomas_regex works on paper, not in real life
hmmm same issue here on my gaming rig. following this thread fingers crossed 🤞
@rusty_hound873 what did u end up doing in the end
oh ive been there lol try turning off teh driver first, fixed it for me
@tomas_regex biggest takeaway: our problem was ownership, not protocol. assigned an owner for the contracts first xD thanks for the thoughtful replies. u guys are the best!!!

sigsegv after a library upgrade: the culprit was three layers down
Related topics
- our four-person team wants protobufs everywhere. should i push back?
- INTERNAL APIS: BORING REST VS SHINY GRPC. CONVINCE ME EITHER WAY
- Is GRPC Worth It For Internal Calls, Or Is That Resume-Driven Design?
- our platform team wants protobufs everywhere. should i push back?
- the one question that settled our rest vs grpc debate
- is it nginx or the spring boot app? a 502 mystery with one clue
Reply to this topic
Sign in or create an account to reply.
