gRPC

gRPC
Developer(s)	Google
Initial release	August 2016
Stable release	1.29.1
Repository	github.com/grpc/grpc;
Written in	Android Java, C#, C++, Dart, Go, Java, Kotlin/JVM, Node.js, Objective-C, PHP, Python, Ruby
Type	Remote procedure call framework
License	Apache License 2.0
Website	grpc.io

gRPC (gRPC Remote Procedure Calls[1]) is an open source remote procedure call (RPC) system initially developed at Google in 2015[2]. 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 microservices style architecture and connect mobile devices, browser clients to backend services.[3]

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

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.[5]

Encoding

gRPC uses protocol buffers to encode the 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.[6]

Adoption

A number of different organizations have adopted gRPC, such as Square, Netflix, CoreOS, Docker, CockroachDB, Cisco, Juniper Networks[7] and Spotify[8].

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

gollark: If someone has a somewhat unconventional computer setup, that means they are a deviant and obviously must be punished.

gollark: Hmm. You can probably passthrough USB devices, or "passthrough" fake ones.

gollark: It will also be hilariously slow.

gollark: As I said, you can trick it into running, probably, by not using any acceleration stuff.

gollark: You probably can trick it into running in a VM anyway, though, fortunately.

References

https://grpc.io/faq#what-does-grpc-stand-for
Introducing gRPC, a new open source HTTP/2 RPC Framework
https://grpc.io/about/
"The state of gRPC in the browser". gRPC.
"gRPC". grpc.io. Retrieved 2020-02-24.
JamesNK. "Compare gRPC services with HTTP APIs". docs.microsoft.com. Retrieved 2020-02-24.
"gRPC". grpc.io. Retrieved 2020-02-24.
"gRPC at Spotify" (PDF). jfokus.se. Retrieved 2020-05-12.
"u-bmc". GitHub.com.
Nigmatullin, Ruslan; Ivanov, Alexey (2019-01-08). "Courier: Dropbox migration to gRPC". Retrieved 2019-01-09.CS1 maint: multiple names: authors list (link)

External links

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.

[1] ttps://grpc.io/faq#what-does-grpc-stand-for

[2] Introducing gRPC, a new open source HTTP/2 RPC Framework

[3] ttps://grpc.io/about/

[4] "The state of gRPC in the browser". gRPC.

[5] "gRPC". grpc.io. Retrieved 2020-02-24.

[6] JamesNK. "Compare gRPC services with HTTP APIs". docs.microsoft.com. Retrieved 2020-02-24.

[7] "gRPC". grpc.io. Retrieved 2020-02-24.

[8] "gRPC at Spotify" (PDF). jfokus.se. Retrieved 2020-05-12.

[ubmc-9] "u-bmc". GitHub.com.

[dropbox-10] Nigmatullin, Ruslan; Ivanov, Alexey (2019-01-08). "Courier: Dropbox migration to gRPC". Retrieved 2019-01-09.CS1 maint: multiple names: authors list (link)