News for hackers. Stuff that matters.
Re:gRPC: The Ugly Parts by tgma on Sunday September 08, 2024 @04:21AM (#41478991)
"Not very dependent" is subjective. The objective relevant take is it is a required dependency of parts of officially supported APIs of major GCP services that have large paid customers with SLAs. It can't go away anytime soon.

Google may have Stubby as the primary internal RPC, but several other large companies rely primarily on gRPC and have contribute to it and have incentives to keep it alive, e.g. Dropbox, Netflix, even parts of Apple and Microsoft. In fact, Microsoft's support of gRPC in C#/.NET is arguably more first-class and polished than any other language.

Re:gRPC: The Ugly Parts by rougka on Monday September 09, 2024 @02:42AM (#41486020)
Fair enough

Although this might have some external implications, most of GCP does not rely on gRPC, even the external customers are not usually dependent on gRPC when using Google services.

Correct me if I'm wrong but gcloud uses REST and so do the libraries google publishes for using GCP apis in different languages.

The question is can Google stop supporting gRPC, protobuf or stubby tomorrow, and I still think gRPC is relatively at risk

Re:gRPC: The Ugly Parts by tgma on Tuesday September 10, 2024 @09:46PM (#41507394)
> so do the libraries google publishes for using GCP apis in different languages

Not true. Many Google Cloud client libraries do support gRPC.

> still think gRPC is relatively at risk

I would agree with you that relative to protobuf and stubby, gRPC is less critical to Google infra. Yet, in absolute terms I would put the probability of that happening for any of those in the next couple decades at zero.

Re:gRPC: The Ugly Parts by rougka on Saturday September 14, 2024 @09:31AM (#41539686)
you are right, I checked now and these are based on gRPC

for some reason I remembered these used REST