3 ms·

gRPC does have native bindings for all of Go, Ruby and Node.js. Not sure why you say it won't work well? NATS being a SPOF isn't necessarily a problem for us i

gRPC does have native bindings for all of Go, Ruby and Node.js. Not sure why you say it won't work well? NATS being a SPOF isn't necessarily a problem for us if it's stable, which it seems to be. We are already completely dependent on HAProxy as a SPOF, anyway. Moreover, most client bindings seem to support providing a host list they use for failover. I will take a closer look at Quark and Datawire Connect when I have a spare moment. Do you have it running in production? Happy to hear that Go is on the roadmap.

rdli 11y ago
gRPC bindings for languages that aren't popular at Google (e.g., Ruby, Node) aren't particularly mature. Each of the different language bindings is independently maintained, so there is no guarantee of feature parity across the languages. We do not have Quark/DC running in production yet. Most of the adoption has been in the realm of testing scenarios (it's super handy to be able to generate client stubs).