gRPC

From Wikipedia, the free encyclopedia
gRPC
Developer(s)Google
Initial releaseAugust 2016; 5 years ago (2016-08)
Stable release
1.43.2[1] / January 27, 2022; 11 days ago (2022-01-27)
Repository
Written inAndroid Java, C#, C++, Dart, Go, Java, Kotlin/JVM, Node.js, Objective-C, PHP, Python, Ruby
TypeRemote procedure call framework
LicenseApache License 2.0
Websitegrpc.io

gRPC (gRPC Remote Procedure Calls[2]) also known as Google Remote Procedure Call is an open source remote procedure call (RPC) system initially developed at Google in 2015 as the next generation of the RPC infrastructure Stubby.[3][4] It uses HTTP/2 for transport, Protocol Buffers as the interface description language, and provides features such as authentication, bidirectional streaming and flow control, blocking or nonblocking bindings, and cancellation and timeouts. It generates cross-platform client and server bindings for many languages. Most common usage scenarios include connecting services in a microservices style architecture, or connecting mobile device clients to backend services.[4]

gRPC's complex use of HTTP/2 makes it impossible to implement a gRPC client in the browser, instead requiring a proxy.[5]

Authentication[]

gRPC supports the usage of TLS and token-based authentication. Connection to Google services must use TLS. There are two types of credentials: channel credentials and call credentials.[6]

Encoding[]

Main article: Protocol Buffers

gRPC uses Protocol Buffers to encode data. Contrary to HTTP APIs with JSON, they have a more strict specification. Due to having a single specification, gRPC eliminates debate and saves developer time because gRPC is consistent across platforms and implementations.[7]

Adoption[]

A number of different organizations have adopted gRPC, such as Uber,[8] Square, Netflix, IBM, CoreOS, Docker, CockroachDB, Cisco, Juniper Networks,[9] Spotify,[10] Zalando[11] and Dropbox.[12]

The open source project u-bmc uses gRPC to replace IPMI.[13] On 8 January 2019, Dropbox announced that the next version of "Courier", their RPC framework at the core of their service-oriented architecture (SOA), would be migrated to be based on gRPC, primarily because it aligned well with their existing custom RPC frameworks.[14]

See also[]

References[]

  1. ^ "gRPC releases". Retrieved 2022-02-07.
  2. ^ "FAQ". gRPC.
  3. ^ "Introducing gRPC, a new open source HTTP/2 RPC Framework".
  4. ^ a b "About gRPC". gRPC. Retrieved 2021-05-25.
  5. ^ "The state of gRPC in the browser". gRPC.
  6. ^ "gRPC". grpc.io. Retrieved 2020-02-24.
  7. ^ JamesNK. "Compare gRPC services with HTTP APIs". docs.microsoft.com. Retrieved 2020-02-24.
  8. ^ "gRPC at Uber".
  9. ^ "gRPC". grpc.io. Retrieved 2020-02-24.
  10. ^ "gRPC at Spotify" (PDF). jfokus.se. Retrieved 2020-05-12.
  11. ^ "Zalando Tech Radar". opensource.zalando.com. Retrieved 2021-04-08.
  12. ^ "How we migrated Dropbox from Nginx to Envoy". Dropbox.Tech. Retrieved 2020-10-30.
  13. ^ "u-bmc". GitHub.com.
  14. ^ Nigmatullin, Ruslan; Ivanov, Alexey (2019-01-08). "Courier: Dropbox migration to gRPC". Retrieved 2019-01-09.

External links[]


Stub icon

This Google-related article is a stub. You can help Wikipedia by .

  • v
  • t
Retrieved from ""