Lecture 191: gRPC & ALB
- 课程：[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长：02:18
- 来源：Udemy Lecture 33170788
- Slide 数量：4
- 画面切换：00:30、01:08、01:44
扫描说明
逐条读取了 Udemy 页面中的 43 条英文 Transcript cue，并按时间轴扫描全长约 02:18 的视频。依据 gRPC/HTTP/2 背景、端到端 ALB 架构、Health Check/Content-based Routing/Streaming 能力、HTTPS Listener 与 NLB 对比划分为 4 个小节。截图均在 Transcript 侧栏关闭、播放器控件隐藏后复核，统一为 1364×770。
Transcript 来自 Udemy 页面自带的英文自动字幕，没有使用 ASR。下面保留页面原文，包括其中的语法或识别错误。
1. ALB 原生支持基于 HTTP/2 的 gRPC
时间范围：00:00–00:30
总结 / Summary
中文
gRPC 是常见的 Microservice Integration 方式，底层使用 HTTP/2。Application Load Balancer 现在能原生理解并完整支持 gRPC；过去为了透传这类流量常使用 Network Load Balancer，而 ALB 的应用层能力让 gRPC 服务可以直接获得 L7 功能。
English
gRPC is a popular microservice-integration approach built on HTTP/2. Application Load Balancer now understands and fully supports gRPC natively. Previously this traffic was commonly passed through a Network Load Balancer, but ALB allows gRPC services to use layer-7 capabilities directly.
Transcript
00:00 So just a quick lecture on gRPC support
00:03 for the Application Load Balancer.
00:05 So gRPC in a word in a sentence is just
00:08 a very popular choice if you want
00:10 microservice integration using HTTP/2.
00:15 So that's the newer way of writing
00:17 APIs using the newer version of HTTP.
00:21 And the Application Load Balancer
00:24 will fully support gRPC which is great because before
00:28 we had to use a Network Load Balancer.
2. 客户端到 ALB、ALB 到 Target 都保持 gRPC/HTTP/2
时间范围：00:30–01:08
总结 / Summary
中文
示例把运行 gRPC Application 的 EC2 Instance 放在跨 AZ Auto Scaling Group 中，并组成 ALB Target Group。User 以 gRPC（HTTP/2）访问 ALB，ALB 再以 gRPC/HTTP/2 路由到 Microservice Target，前后端协议都保持 Native，不需要把请求降级为 HTTP/1。1。
English
The example places EC2 instances running a gRPC application in a cross-AZ Auto Scaling group and registers them in an ALB target group. Users reach the ALB with gRPC over HTTP/2, and the ALB routes to the microservice targets with gRPC/HTTP/2 as well, preserving native protocol behavior end to end.
Transcript
00:30 So how does it work? Well, we have our deployment.
00:34 We have, for example, EC2 instances,
00:36 that are running in an Auto Scaling group.
00:38 And these EC2 instances represent a microservice,
00:42 and on the instances we are running an application
00:45 that is fully supporting gRPC.
00:48 So the users can now access directly our ALB
00:52 using the gRPC protocol, which is behind the scenes HTTP/2
00:56 and the ALB will know how to do routing
01:00 to your microservice using the gRPC protocol as well.
01:04 Everything is gRPC native and HTTP/2 native.
3. 获得 gRPC Health Check、内容路由与双向 Streaming
时间范围：01:08–01:44
总结 / Summary
中文
ALB 可对 Target Group 执行 gRPC-aware Health Check，并利用 Content-based Routing 把多个 Microservice 的请求发往正确 Service。由于底层是 HTTP/2，它还支持各类 gRPC Communication，包括 Bidirectional Streaming。这些都是选择 ALB 而非只做四层转发的核心收益。
English
ALB can perform gRPC-aware target-group health checks and use content-based routing to direct requests among multiple microservices. Because gRPC runs on HTTP/2, ALB also supports gRPC communication patterns including bidirectional streaming. These are major benefits over simple layer-4 forwarding.
Transcript
01:08 So why am I saying this? Well, because we are using an ALB.
01:11 That means that we can do health checks directly from
01:14 the application balancer directly into your target group,
01:18 and that supports the gRPC protocol of course.
01:21 Also you can do content based routing
01:23 to route to the appropriate service
01:26 if you have multiple microservices behind a single ALB.
01:30 It supports all kind of gRPC communication.
01:33 So because we are using HTTP/2
01:35 we can get, for example, bidirectional streaming,
01:38 and that is a feature that is provided
01:40 as part of the ALB, and this is gRPC specific.
4. ALB Listener 必须是 HTTPS；NLB 可用但缺少 HTTP 特性
时间范围：01:44–02:18
总结 / Summary
中文
课程强调 ALB 承载 gRPC 时 Listener Protocol 只能使用 HTTPS。gRPC 也可以通过 NLB 工作，但 NLB 不提供 ALB 的 HTTP-specific Feature，例如 Application-aware Health Check 和 Content-based Routing。因此，需要 L7 检查、按内容分流或原生 gRPC 可观测性时优先 ALB。
English
The course emphasizes that an ALB carrying gRPC must use HTTPS as its listener protocol. gRPC can also work through an NLB, but the NLB lacks ALB HTTP-specific features such as application-aware health checks and content-based routing. Prefer ALB when layer-7 inspection, content routing, or native gRPC visibility is required.
Transcript
01:44 And you can only use on the ALB
01:47 the HTPS protocol, nothing else. Okay? For listeners.
01:52 Now. gRPC would also work with any Network Load Balancer,
01:58 but the advantage of using the application balancer
02:01 over the Network Load Balancer
02:04 is that the application balancer provides you
02:06 a lot of what I call HTTP specific features
02:09 such as the health checks, the content based routing
02:12 and so on. Okay. That's it for this lecture.
02:15 I hope you liked it. And I will see you in the next lecture.
整讲总结 / Overall Summary
中文
ALB 能端到端承载 gRPC/HTTP/2，并提供 gRPC Health Check、Content-based Routing 与 Bidirectional Streaming；Listener 必须使用 HTTPS。NLB 也能转发 gRPC，但缺少这些 HTTP/L7 特性，因此架构选择取决于是否需要应用层路由和健康检查。
English
ALB carries gRPC/HTTP/2 end to end and provides gRPC health checks, content-based routing, and bidirectional streaming; its listener must use HTTPS. NLB can forward gRPC too, but lacks these HTTP/layer-7 features, so the architecture choice depends on whether application-aware routing and health checks are needed.
返回顶部 ↑