Misplaced Pages

gRPC (recursive acronym for gRPC Remote Procedure Calls) is a cross-platform high-performance remote procedure call (RPC) framework. gRPC was initially created by Google, but is open source and is used in many organizations. Use cases range from microservices to the "last mile" of computing (mobile, web, and Internet of Things). gRPC 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.

As of 2019, gRPC's use of HTTP/2 makes it impossible to implement a gRPC client in a browser, instead requiring a proxy.

History

From about 2001, Google created a general-purpose RPC infrastructure called Stubby to connect the large number of microservices running within and across its data centers. In March 2015, Google decided to build the next version of Stubby and make it open source. The result was gRPC.

Authentication

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 and a Client Interceptor.

Encoding

gRPC uses Protocol Buffers to encode data. Protocol buffers provide a serialization format and an Interface Definition Language.

Testing

Some of the software tools used for testing gRPC implementations include Postman, ezy, Insomnia, and Step CI.

Adoption

Many organizations use gRPC, including Uber, Square, Netflix, IBM, CoreOS, Docker, CockroachDB, Arista Networks, Cisco, Juniper Networks, Spotify, Zalando, Dropbox, and Google as the original developer.

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

Alternatives

• Cap'n Proto
• Apache Thrift
• Apache Avro
• JSON-RPC
• XML-RPC

See also

• Comparison of data serialization formats

References

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

External links

• gRPC Home Page
• gRPC – github.com
• gRPC – opensource.google.com

• Remote procedure call
• Software using the Apache license
• Google software
• Free software programmed in C++
• Free software programmed in Python