imported>Yumeto：使用DisamAssist清理消歧義連結：Go（改連結至Go語言）。

2026-03-02T15:26:18Z

新页面

{{Infobox software
| name = gRPC
| title = gRPC
| developer = [[Google]]
| latest_release_version = 1.45.0<ref name="grpc-releases">{{cite web|url=https://github.com/grpc/grpc/releases|title=gRPC releases|accessdate=2022-02-07|archive-date=2022-05-04|archive-url=https://web.archive.org/web/20220504125840/https://github.com/grpc/grpc/releases}}</ref>
| latest release date = {{Start date and age|2022|03|19}}
| released = {{Start date and age|2016|08}}
| programming language = [[Android]] [[Java]]、[[C♯]]、[[C++]]、[[Dart]]、[[Go語言|Go]]、[[Java]]、[[Kotlin]]/[[Java虚拟机|JVM]]、[[Node.js]]、[[Objective-C]]、[[PHP]]、[[Python]]、[[Ruby]]
| genre = [[遠端程序呼叫]][[軟體框架|框架]]
| license = [[Apache License 2.0]]
| website = {{URL|https://grpc.io/}}
}}
{{NoteTA
|G1=IT
|1=zh-tw:使用案例;zh-cn:用例
|2=zh-tw:用戶端;zh-cn:客户端
}}
{{Lowercase}}'''gRPC''' ('''gRPC''' '''Remote Procedure Calls'''<ref>{{Cite web |title=FAQ |url=https://grpc.io/docs/what-is-grpc/faq/ |website=gRPC |language=en |access-date=2022-10-10 |archive-date=2022-01-04 |archive-url=https://web.archive.org/web/20220104231953/https://grpc.io/docs/what-is-grpc/faq/ |dead-url=no }}</ref>) 是一个[[跨平台]]的[[开源]]高性能[[遠程過程調用|远程过程调用]]（'''RPC'''）框架。

gRPC最初由[[Google]]创建，它使用一个通用的RPC基础设施Stubby来连接其[[数据中心]]内外运行的大量[[微服務|微服务]]，始于2001年。<ref>{{Cite web|title=gRPC: a true internet-scale RPC framework is now 1.0 and ready for production deployments|url=https://cloud.google.com/blog/products/gcp/grpc-a-true-internet-scale-rpc-framework-is-now-1-and-ready-for-production-deployments|date=24 August 2016|access-date=2023-04-03|archive-date=2024-01-23|archive-url=https://web.archive.org/web/20240123205146/https://cloud.google.com/blog/products/gcp/grpc-a-true-internet-scale-rpc-framework-is-now-1-and-ready-for-production-deployments|dead-url=no}}</ref>2015年3月，Google决定构建下一个版本的Stubby并将其开源，于是就有了gRPC。现在除了Google之外，许多组织都在使用它来支持从微服务到计算的“最后一英里”（移动、Web和物联网）的用例。

gRPC基于[[HTTP/2]]协议传输数据，使用[[Protocol Buffers]]作为[[接口描述语言]]，并提供认证（authentication）、双向[[字符串|串流]]（bidirectional streaming）和[[數據流量控制|流量控制]]、阻塞或非阻塞绑定以及取消和超时（Deadlines）等功能。它为许多语言生成跨平台的客户端和服务器绑定。最常见的使用场景包括在微服务风格的架构中连接服务，或将移动设备客户端连接到后端服务。<ref name=":0">{{Cite web|title=About gRPC|url=https://grpc.io/about/|website=gRPC|language=en|access-date=2021-05-25|archive-date=2020-12-22|archive-url=https://web.archive.org/web/20201222032503/https://grpc.io/about/|dead-url=no}}</ref>

gRPC对HTTP/2的复杂使用使得在浏览器中无法实现gRPC客户端，而需要使用代理。<ref>{{cite web|title=The state of gRPC in the browser|url=https://grpc.io/blog/state-of-grpc-web/|website=gRPC|date=8 January 2019|language=en-us|access-date=2024-03-02|archive-date=2022-01-04|archive-url=https://web.archive.org/web/20220104231953/https://grpc.io/blog/state-of-grpc-web/|dead-url=no}}</ref>

最常见的应用场景是<ref>{{Cite web |title=About gRPC |url=https://grpc.io/about/ |website=gRPC |language=en |access-date=2022-10-10 |archive-date=2020-12-22 |archive-url=https://web.archive.org/web/20201222032503/https://grpc.io/about/ |dead-url=no }}</ref>：

* [[微服务]]框架下，多种语言服务之间的高效交互。
* 将手机服务、浏览器连接至后台
* 产生高效的客户端库

== 身份验证（Authentication） ==
gRPC支持使用[[传输层安全性协定|传输层安全性协议]]（TLS）和基于令牌的身份验证。连接到Google服务必须使用TLS。有两种类型的凭据：通道凭据和调用凭据。对于基于令牌的授权，gRPC提供了服务器拦截器<ref>{{Cite web|title=gRPC Server Interceptor|url=https://thecodedata.com/grpc-interceptors-with-java/|access-date=2024-03-02|archive-date=2024-06-09|archive-url=https://web.archive.org/web/20240609164121/https://thecodedata.com/grpc-interceptors-with-java/|dead-url=no}}</ref>和客户端拦截器<ref>{{Cite web|title=gRPC|url=https://grpc.io/docs/guides/auth/|website=grpc.io|access-date=2020-02-24|archive-date=2022-01-04|archive-url=https://web.archive.org/web/20220104231957/https://grpc.io/docs/guides/auth/|dead-url=no}}</ref>。

== 编码（Encoding） ==
{{Main|Protocol Buffers}}gRPC使用[[Protocol Buffers]]来编码数据。Protocol buffers提供了一种序列化格式和[[接口描述语言]]。<ref>{{Cite web|title=Compare gRPC services with HTTP APIs|url=https://docs.microsoft.com/en-us/aspnet/core/grpc/comparison|website=docs.microsoft.com|language=en-us|last=JamesNK|access-date=2020-02-24|archive-date=2023-12-07|archive-url=https://web.archive.org/web/20231207014758/https://learn.microsoft.com/en-us/aspnet/core/grpc/comparison?view=aspnetcore-8.0|dead-url=no}}</ref>

== 测试（Testing） ==
用于测试gRPC实现的一些软件工具包括[[Postman]]、ezy<ref>{{cite web|title=ezy on GitHub|url=https://github.com/getezy/ezy|access-date=2024-03-02|archive-date=2024-03-27|archive-url=https://web.archive.org/web/20240327124111/https://github.com/getezy/ezy|dead-url=no}}</ref>、Insomnia和Step CI<ref>{{cite web|title=Step CI Documentation|url=https://docs.stepci.com/guides/testing-grpc.html|access-date=2024-03-02|archive-date=2023-12-06|archive-url=https://web.archive.org/web/20231206052837/https://docs.stepci.com/guides/testing-grpc.html|dead-url=no}}</ref>。

== 应用 ==
许多不同的组织已经采用了gRPC，例如[[Uber]],<ref>{{cite web|title=gRPC at Uber|url=https://eng.uber.com/architecture-api-gateway/|date=19 May 2021}}</ref> [[Square, Inc.|Square]], [[Netflix]], [[IBM]], [[CoreOS]], [[Docker (software)|Docker]], [[CockroachDB]], [[Arista Networks]], [[Cisco Systems|Cisco]], [[Juniper Networks]],<ref>{{Cite web|title=gRPC|url=https://grpc.io/faq/#who-s-using-this-and-why|website=grpc.io|access-date=2020-02-24|archive-date=2020-11-24|archive-url=https://web.archive.org/web/20201124225231/https://grpc.io/faq/#who-s-using-this-and-why|dead-url=no}}</ref> [[Spotify]],<ref>{{Cite web|title=gRPC at Spotify|url=https://www.jfokus.se/jfokus19-preso/Adopting-gRPC-at-Spotify.pdf|website=jfokus.se|access-date=2020-05-12|archive-date=2021-10-27|archive-url=https://web.archive.org/web/20211027132839/https://www.jfokus.se/jfokus19-preso/Adopting-gRPC-at-Spotify.pdf|dead-url=no}}</ref> [[Zalando]],<ref>{{Cite web|title=Zalando Tech Radar|url=https://opensource.zalando.com/tech-radar/|website=opensource.zalando.com|access-date=2021-04-08|archive-date=2021-10-20|archive-url=https://web.archive.org/web/20211020013502/https://opensource.zalando.com/tech-radar/|dead-url=no}}</ref> [[Dropbox (service)|Dropbox]],<ref>{{Cite web|title=How we migrated Dropbox from Nginx to Envoy|url=https://dropbox.tech/infrastructure/how-we-migrated-dropbox-from-nginx-to-envoy|website=Dropbox.Tech|access-date=2020-10-30|archive-date=2022-01-04|archive-url=https://web.archive.org/web/20220104231954/https://dropbox.tech/infrastructure/how-we-migrated-dropbox-from-nginx-to-envoy|dead-url=no}}</ref> 以及作为原始开发者的Google。

开源项目 [[OpenBMC#u-bmc|u-bmc]] 使用gRPC替代[[IPMI|智能平台管理接口]]（IPMI）。<ref name="ubmc">{{cite web|title=u-bmc|url=https://github.com/u-root/u-bmc|website=GitHub.com|date=5 October 2022|access-date=2024-03-02|archive-date=2022-01-04|archive-url=https://web.archive.org/web/20220104231952/https://github.com/u-root/u-bmc|dead-url=no}}</ref>2019年1月8日，[[Dropbox]]宣布他们的[[面向服务的体系结构|服务导向架构]]（SOA）核心的RPC框架“Courier”的下一个版本将迁移到gRPC上，主要是因为它与他们现有的自定义RPC框架很好地契合。<ref name="dropbox">{{cite web|title=Courier: Dropbox migration to gRPC|url=https://blogs.dropbox.com/tech/2019/01/courier-dropbox-migration-to-grpc/|date=2019-01-08|author=Nigmatullin, Ruslan|author2=Ivanov, Alexey|access-date=2019-01-09|archive-date=2020-03-12|archive-url=https://web.archive.org/web/20200312221046/https://blogs.dropbox.com/tech/2019/01/courier-dropbox-migration-to-grpc/|dead-url=no}}</ref>

== gRPC的替代方案 ==

* [[Cap'n Proto]]
* [[Apache Thrift]]
* [[Apache Avro]]
* [[JSON-RPC]]
* [[XML-RPC]]

== 参见 ==
* {{Ilh/en|数据序列化格式的比较|Comparison_of_data-serialization_formats|数据序列化格式的比较}}

== 参考文献 ==
<references />

== 外部链接 ==
* [https://grpc.io/ gRPC – 官方网站] {{Wayback|url=https://grpc.io/ |date=20210123195333 }}
* [https://opensource.google/projects/grpc gRPC – opensource.google.com] {{Wayback|url=https://opensource.google/projects/grpc |date=20201201003248 }}
* [https://github.com/grpc/ gRPC – GitHub] {{Wayback|url=https://github.com/grpc/ |date=20220104231956 }}
* [https://doc.oschina.net/grpc 开源中国 gRPC文档中文翻譯版] {{Wayback|url=https://doc.oschina.net/grpc |date=20201030195528 }}

{{Google FOSS}}
{{google-stub}}

[[Category:Google軟體]]
[[Category:使用BSD许可证的软件]]
[[Category:遠端程序呼叫]]

GRPC - 版本历史

imported>Yumeto：​使用DisamAssist清理消歧義連結：Go（改連結至Go語言）。

imported>Yumeto：使用DisamAssist清理消歧義連結：Go（改連結至Go語言）。