RPC via GRPC?
Have y'all thought about integrating GRPC as the method of communicating between the front and backend? It is probably overkill right now since most devs are not used to types anyways, but I feel like with the way that you are generating the server/client rpc connectors, GRPC would be a good candidate to make that process more streamlined. You could use the GRPC json gateway to keep the browser and server comms something that is easily debugable. https://github.com/grpc-ecosystem/grpc-gateway I don't think it has a place in wasp at the moment (given that you want to tap into the rapid prototype market), but it is a consideration that I would make when you think about how a project grows in complexity.
GitHub
GitHub - grpc-ecosystem/grpc-gateway: gRPC to JSON proxy generator ...
gRPC to JSON proxy generator following the gRPC HTTP spec - GitHub - grpc-ecosystem/grpc-gateway: gRPC to JSON proxy generator following the gRPC HTTP spec
4 Replies
gRPC sounds very interesting for sure, thanks!
I think you are right that at the moment it is a bit much, since we are focusing on other stuff at the moment, but as time goes we do want to offer more for the bigger apps and those in enterprise settings, so this might become a thing to work on!
Curious if there's been further thoughts on grpc
We are not planning on integrating it in the near future or using it as the default, but! That shouldn't stop you from using it yourself for any use case you might find it necessary for 🙂
Did you try integrating it in Wasp maybe already? What kind of use cases are you looking to support? We are interested in learning more 🙂
@ayo Also, if I may ask, are you developing for web or mobile?