Why Segment Chose Go, gRPC, and Envoy to Build Their New Config API

Re:Why Segment Chose Go, gRPC, and Envoy to Build Their New ... by DandyDev on Saturday December 15, 2018 @03:10AM (#18687588)

This might be a dumb question, but why translate REST to gRPC and not expose the gRPC services directly?

[ Parent | on HN ]

Re:Why Segment Chose Go, gRPC, and Envoy to Build Their New ... by buckhx on Saturday December 15, 2018 @03:20AM (#18687617)

Browsers don't speak grpc natively. There is a separate spec for browser support, but it's a very new project https://github.com/grpc/grpc-web/blob/master/README.md

[ Parent | on HN ]

Re:Why Segment Chose Go, gRPC, and Envoy to Build Their New ... by nzoschke on Saturday December 15, 2018 @01:44PM (#18689687)

OP here. We considered this, but decided against it for a couple reasons.

First and foremost our customers universally favor REST APIs. GraphQL and gRPC are better tech wise but REST is more familiar.

Next gRPC uses pure HTTP/2 which doesn’t work with an AWS ALB.

Thanks to the grpc ecosystem the HTTP/1 and REST transcoding is just an Envoy config.

[ Parent | on HN ]