Re:gRPC-Web: Moving past REST+JSON towards type-safe Web APIs
by lyschoening on Thursday April 27, 2017 @07:25AM
(#14210681)
It is worth pointing out that the Python implementation is particularly bad. Perhaps gRPC is really pleasant to use with Java and Go, but the Python implementation is neither usable nor stable enough for it to be worth considering its use for one's own services.
[ Parent
| on HN ]
Re:gRPC-Web: Moving past REST+JSON towards type-safe Web APIs
by mwitkow on Thursday April 27, 2017 @08:43AM
(#14210989)
We haven't tried using gRPC in Python, as we have completely migrated from Python away towards Go.
Our experience of using gRPC in Java, C++ and Golang is pretty good. While it had some initial teething issues (when it was first released), the libraries have generally been a non-issue since the gRPC General Availability (GA-1.0 version).
If you're considering using it in Go, check out the https://github.com/grpc-ecosystem/go-grpc-middleware helper libraries that we've contributed back to gRPC Ecosystem.
Re:gRPC-Web: Moving past REST+JSON towards type-safe Web APIs
by fishnchips on Thursday April 27, 2017 @08:58AM
(#14211077)
Ruby too was pretty bad - more so Protocol Buffers than gRPC itself though. In my previous place, I had to fork the Ruby library and write a non-trivial amount of C code so that instances of Protocol Buffers messages could be treated as regular Ruby objects by their callers. Once I opened a PR against upstream it was quickly accepted but took some 6 months to be published to Ruby Gems. I'm not saying to stay away, but please be prepared for surprises.
Re:gRPC-Web: Moving past REST+JSON towards type-safe Web APIs
by JayOtter on Thursday April 27, 2017 @08:36AM
(#14210967)
My instinct would be that it'll be just inherently nicer to use in a statically-typed language.
Re:gRPC-Web: Moving past REST+JSON towards type-safe Web APIs
by lyschoening on Friday April 28, 2017 @04:32AM
(#14217830)
Python can be statically typed.