3 ms·
"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
by tgma 2y ago
"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.
- rougka 2y agoFair 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
- tgma 2y ago> 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.
- rougka 2y agoyou are right, I checked now and these are based on gRPC for some reason I remembered these used REST