The state of gRPC in the browser

Re:The state of gRPC in the browser by helipaddi on Wednesday January 09, 2019 @04:00PM (#18868836)

Could someone explain the difference between gRPC and Apache Thrift? Even tough the Apache Thrift project is not as active as gRPC it works quite well for us.

[ Parent | on HN ]

Re:The state of gRPC in the browser by q3k on Wednesday January 09, 2019 @07:36PM (#18870506)

Thrift is what xooglers at Facebook implemented when they wanted Stubby. grpc is Google's own open source edition of Stubby.

They are very similar paradigm-wise.

[ Parent | on HN ]

Re:The state of gRPC in the browser by jholman on Thursday January 10, 2019 @12:30PM (#18875820)

Wait, what? IIRC Stubby is a lockserver, used for two things: coordinated locks, and small coordinated data. You mean protobuff, don't you? Am I misremembering and/or wrong?

[ Parent | on HN ]

Re:The state of gRPC in the browser by deklerk on Thursday January 10, 2019 @01:03PM (#18876229)

You're thinking of chubby. :) https://ai.google/research/pubs/pub27897

[ Parent | on HN ]

Re:The state of gRPC in the browser by anderspitman on Wednesday January 09, 2019 @04:53PM (#18869334)

I think they're rather similar in goals. I found this overview informative: https://youtu.be/RoXT_Rkg8LA

[ Parent | on HN ]

Re:The state of gRPC in the browser by throaaway1984 on Wednesday January 09, 2019 @05:40PM (#18869750)

gRPC is protocol agnostic. You can use any wire type with it, like JSON. There's even a codec for thrift messages on gRPC called grift.

[ Parent | on HN ]

Re:The state of gRPC in the browser by Matthias247 on Thursday January 10, 2019 @02:51AM (#18872246)

The main difference: grpc can do bidirectional streaming, and not only request-response RPC.

[ Parent | on HN ]