Grpc frequently asked questions

What is? gRPC？

gRPC It's a modern 、 Open source remote procedure calls (RPC) frame , Can run anywhere . It enables client and server applications to communicate transparently , And make it easier to build a connection system .

gRPC What is the ？

gRPC Remote Procedure Calls, of course!
Certainly gRPC Remote procedure call !

Why should I use gRPC？

Main use scenarios ：

Low latency 、 Highly scalable distributed systems .
Develop mobile clients to communicate with cloud servers .
Designing one needs to be accurate 、 Efficient and language independent new protocol .
Layered design for expansion , for example . Authentication 、 Load balancing 、 Logging and monitoring, etc .

Who is using it , Why? ？

gRPC Is a cloud native Computing Foundation (CNCF) project .

For a long time ,Google Always in use gRPC Many underlying technologies and concepts in . The current implementation is used in several Google cloud products and Google's external facing API.Square, Netflix, CoreOS, Docker, CockroachDB, Cisco, Juniper Networks as well as Many other organizations and individuals are using it .

Which programming languages are supported ？

Please refer to the officially supported languages and platforms .

How to get started gRPC？
You can follow the instructions here to start the installation gRPC . Or go to gRPC GitHub Organize pages , Select the runtime or language you are interested in , And then according to README Explain how to operate .

gRPC Under which license ？

All implementations are Apache 2.0 Get permission under .

How can I contribute ？

Contributors are very welcome , The repository is hosted in GitHub On . We expect feedback from the community 、 Additions and errors . Both individual and corporate contributors need to sign our CLA. If you are right about gRPC Project ideas , Please read the guide and submit it here . We are gRPC There are more and more project lists under the ecosystem GitHub Organizations on the Internet .

Where is the document ？

stay grpc.io Check the document on .

What is the road map ？

gRPC The project has a RFC technological process , Design and approve the implementation of new functions through this process . They are tracked in this repository .

gRPC How long does the version support ？

gRPC The project will not be carried out LTS Release . In view of the above rolling release model , We support the current 、 Latest and previous versions . Support here means bug fixes and security fixes .

What is? gRPC Version control strategy ？

Check out here gRPC Version control strategy . https://github.com/grpc/grpc/blob/master/doc/versioning.md

Abreast of the times gRPC What is the version ？

The latest release label is v1.46.3.

gRPC When to release ？

gRPC The project in master The tip of the branch always works in a stable model . The project （ Across various runtimes ） Aims to do our best every 6 The checkpoint version is released once a week . View the release schedule here .

How to report gRPC Security holes in ？

To report gRPC Security holes in , Please follow the process recorded here .https://github.com/grpc/proposal/blob/master/P4-grpc-cve-process.md

Can I use it in my browser ？

gRPC -Web Projects are universally available .

I can put gRPC With my favorite data format （JSON、Protobuf、Thrift、XML） Use it together ？

Yes .gRPC Designed to be extensible to support multiple content types . The initial version contains a pair of Protobuf And external support for other content types , for example FlatBuffers and Thrift, At different levels of maturity .

I can use... In the service grid gRPC Do you ？

Yes .gRPC Applications can be deployed in the service grid like any other application .gRPC And support xDS API This makes it impossible to sidecar The agent is deployed in the service grid gRPC Applications become possible .gRPC The supported agent free service grid functions are listed here .

gRPC How to help mobile application development ？

gRPC and Protobuf It provides a simple way to define services precisely and provide services for iOS、Android And the server that provides the back end automatically generates a reliable client library . Clients can use advanced streaming and connection functions to help save bandwidth , Through less TCP Connect to do more , And save CPU Usage and battery life .

Why? gRPC Than HTTP/2 Any binary on blob Better ？

This is to a great extent gRPC Online content . However ,gRPC It's also a set of Libraries , They will be in general HTTP Libraries usually do not provide a higher level of functionality consistently across platforms . Examples of such features include ：

Interact with flow control at the application layer
Cascade call cancellation
Load balancing and failover

Why? gRPC Than REST Better / Worse ？

gRPC To a large extent follow HTTP/2 Above HTTP semantics , But we explicitly allow full duplex streaming . We are with the typical REST The agreement is different , Because we use static paths during call scheduling for performance reasons , Because from the path 、 Parsing call parameters in query parameters and payload body increases latency and complexity . We also formalized a set of errors , We think these mistakes are better than HTTP Status codes are more directly applicable to API Use cases .

How do you pronounce gRPC？

Jee-Arr-Pee-See.