Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Remind me why are you using Grpc?
Plain CRUD/json not good enough?
I hope you are dealing with 1kk messages daily to justify the grpc route.
Grpc is really good for reducing communications/processing overheads for server and client, at specific cost - size limits, and protocol structure changes.
setting it up can be a pain, especilly when you need to use plugins. The best approach I found to solve the generation problems is to:
1. Generate once, using a single good setup (automation). Push to git. Pull to all devs. in case of proto changes, repeat the process.
2. Generate the protos in a docker image based on linux, or a dedicated linux vm/actual machine. rsync the generated code to your local dev env.
The docker approach is better.