gRPC (gRPC Remote Procedure Calls[2]) is a cross-platform open source high performance remote procedure call (RPC) framework. gRPC was initially created by Google, which used a single general-purpose RPC infrastructure called Stubby to connect the large number of microservices running within and across its data centers from about 2001.[3] In March 2015, Google decided to build the next version of Stubby and make it open source. The result was gRPC, which is now used in many organizations aside from Google to power use cases from microservices to the “last mile” of computing (mobile, web, and Internet of Things). 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]

Initial releaseAugust 2016; 7 years ago (2016-08)
Stable release
1.57.0[1] / August 9, 2023; 53 days ago (2023-08-09)
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

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

Authentication Edit

gRPC supports the usage of Transport Layer Security (TLS) and token-based authentication. Connection to Google services must use TLS. There are two types of credentials: channel credentials and call credentials. For token-based authorization, gRPC provides Server Interceptor [6] and a Client Interceptor.[7]

Encoding Edit

gRPC uses Protocol Buffers to encode data. Contrary to REST 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.[8][editorializing]

Adoption Edit

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

The open source project u-bmc uses gRPC to replace Intelligent Platform Management Interface (IPMI).[14] 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.[15]

Alternatives to gRPC Edit

See also Edit

References Edit

  1. ^ "gRPC releases". GitHub. Retrieved 2023-08-17.
  2. ^ "FAQ". gRPC.
  3. ^ "gRPC: a true internet-scale RPC framework is now 1.0 and ready for production deployments". 24 August 2016. Retrieved 2023-04-03.
  4. ^ "About gRPC". gRPC. Retrieved 2021-05-25.
  5. ^ "The state of gRPC in the browser". gRPC. 8 January 2019.
  6. ^ "gRPC Server Interceptor".
  7. ^ "gRPC". Retrieved 2020-02-24.
  8. ^ JamesNK. "Compare gRPC services with HTTP APIs". Retrieved 2020-02-24.
  9. ^ "gRPC at Uber". 19 May 2021.
  10. ^ "gRPC". Retrieved 2020-02-24.
  11. ^ "gRPC at Spotify" (PDF). Retrieved 2020-05-12.
  12. ^ "Zalando Tech Radar". Retrieved 2021-04-08.
  13. ^ "How we migrated Dropbox from Nginx to Envoy". Dropbox.Tech. Retrieved 2020-10-30.
  14. ^ "u-bmc". 5 October 2022.
  15. ^ Nigmatullin, Ruslan; Ivanov, Alexey (2019-01-08). "Courier: Dropbox migration to gRPC". Retrieved 2019-01-09.

External links Edit