Not OP but in same situation. Not every platform can run gRPC over localhost easily or without extra privileges.
replyI used to use protobuf but now I just use JSON, over stdin/stdout on desktop. It’s honestly quite good.
Which platforms? My product runs gRPC client/server on macOS, Linux and Windows. No issues with privileges. Or are you trying to run it on port 443? Yeah, don't do that, run it on 8443 or whatever instead.
replyThen you have to deal with port collisions when some other software wants to use that port. And keeping a port open without any authentication is terrible for security, even if it only binds on localhost, so you have to find some secure way to share a key between the client and server.
replyPersonally I wish we could just use UNIX sockets for "localhost-only TCP", but software support is just not there.
I don't worry about security too much given it is just bound to localhost, but I do use a simple password (and make it modifiable by the user). Avoiding port collisions in the real world isn't a big issue, just ask an AI for the least assigned default ports and chance of collision is minor (in worst case, also user modifiable). In return, you get free "remotability", which is kind of a big deal IMO.
replyI do wish gRPC allowed for easy usage of UNIX domain sockets and perhaps named pipes, however. Sometimes all you need is IPC, but in my case, I'm happy to have remote usage builtin.
Why not ConnectRPC? It's basically gRPC but without all the strange requirements for exotic HTTP features.
replyI've never heard of ConnectRPC before! Will check it out.
replyI actually use this currently. Not nearly as many platforms, but you an always fallback to gRPC.
replyYeah! I'm using a gRPC daemon on PC and go mobile bindings on mobile.
replyMost of the gRPC implementations force buffering of the whole response for large unary responses. They are not really written by people who care about performance. It’s dumb because the protobuf binary marshaled format is perfectly designed for server-side incremental marshaling.
replyPerformance is relative. gRPC is plenty fast enough for my use case, and for that matter, almost all client/server use cases that work across the Internet. If a Javascript web client against a REST backend is fast enough latency-wise, then a local gRPC connection on a single PC is gonna feel like greased lightning. Of course, there will be a few scenarios where tight coupling of client/server are required for good enough performance, but they are few and far between.
reply