HTTP/2 与协议缓冲：gRPC 的基础
了解让 gRPC 高速运行的两项技术：HTTP/2 传输和协议缓冲二进制序列化。
HTTP/2 与协议缓冲：gRPC 的基础 是 CoddyKit 上的免费 gRPC & High Performance APIs 课时。 这是第 4 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 gRPC & High Performance APIs 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 gRPC & High Performance APIs 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
What Powers gRPC
gRPC's speed comes from two pieces: HTTP/2 for transport and Protocol Buffers for serialization. Together they explain why it beats JSON-over-HTTP/1.1.
HTTP/1.1 Limits
HTTP/1.1 sends one request per connection at a time; pipelining is fragile and head-of-line blocking forces many connections. That's latency and overhead for chatty APIs.
HTTP/2 Multiplexing
HTTP/2 multiplexing sends many concurrent streams over one connection. Requests stop blocking each other, and it's what enables gRPC's bidirectional streaming.
Binary Framing & Header Compression
HTTP/2 frames data in binary and compresses headers with HPACK. Fewer bytes on the wire plus cheaper parsing means lower latency than text-based HTTP/1.1.
What Are Protocol Buffers?
Protocol Buffers is a compact, schema-driven binary format. You define messages once in a .proto file and tooling generates code in many languages.
message User {
int32 id = 1;
string name = 2;
bool active = 3;
}Field Numbers Matter
On the wire each protobuf field carries a tag number, not its name — that's what keeps payloads tiny. Never reuse or change a tag, or you break compatibility.
Why Protobuf Is Small & Fast
Protobuf stays small and fast by dropping field names from the payload, using varint encoding for integers, and skipping JSON's whitespace and quotes.
Schema-First Contracts
The .proto file is a strong contract shared by client and server. Both generate type-safe code from it, killing a whole class of loosely-typed JSON bugs.
Putting It Together in gRPC
A gRPC call maps cleanly: the method is an HTTP/2 stream, request and response messages are protobuf bytes, and streaming uses multiple frames on that stream.
service UserService {
rpc GetUser (UserRequest) returns (User);
}Trade-offs
The trade-offs: binary payloads aren't human-readable, browsers need a grpc-web proxy, and you need codegen tooling. For internal high-throughput services, usually worth it.
Why It Beats JSON/REST
Summed up: gRPC wins because HTTP/2 multiplexes efficiently and protobuf serializes compactly, while a shared schema keeps both ends type-safe.
Quick Check
Test your understanding of gRPC's foundation.
Recap
gRPC's two foundations: HTTP/2 brings multiplexed streams and binary framing, while Protocol Buffers give a compact, schema-first format. Together: faster and type-safe.
用 AI 导师学习 gRPC & High Performance APIs — 免费
在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。
- 课程
- 12
- 课程
- 48
常见问题解答
「HTTP/2 与协议缓冲：gRPC 的基础」课时是免费的吗？
是的 — 「HTTP/2 与协议缓冲：gRPC 的基础」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 gRPC & High Performance APIs 课程的其余内容，请升级到 CoddyKit PRO。 gRPC & High Performance APIs 课程共包含 4 节课。
「HTTP/2 与协议缓冲：gRPC 的基础」这节课中我会学到什么？
了解让 gRPC 高速运行的两项技术：HTTP/2 传输和协议缓冲二进制序列化。 你通过在浏览器中直接运行的动手代码来练习 gRPC & High Performance APIs，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 gRPC & High Performance APIs 需要有经验吗？
无需任何先前经验。CoddyKit 上的 gRPC & High Performance APIs 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 4 节课，共 4 节。
「HTTP/2 与协议缓冲：gRPC 的基础」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 gRPC & High Performance APIs 课中编写并运行代码吗？
能。每节 gRPC & High Performance APIs 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。
此课程中的所有课时
- 为什么需要高性能 API
- 什么是 gRPC
- RPC 与 REST 概览
- HTTP/2 与协议缓冲：gRPC 的基础