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.
reply