gRPC & High Performance APIs · 课时

使用 gRPC 设计实时聊天后端

通过真实案例学习：使用 gRPC 双向流、扇出和在线状态，构建可扩展的实时聊天后端架构。

使用 gRPC 设计实时聊天后端 是 CoddyKit 上的免费 gRPC & High Performance APIs 课时。这是第 4 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 gRPC & High Performance APIs 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 gRPC & High Performance APIs 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

The Case Study

We design a chat backend that must deliver messages instantly to thousands of connected users. gRPC bidirectional streaming is a natural fit for this long-lived, two-way flow.

Defining the Service

The core is a bidi stream: clients send messages and receive others' messages over the same call.

service Chat {
  rpc Connect(stream ClientEvent) returns (stream ServerEvent);
}

Per-Connection Sessions

Each open stream is a user session. The server tracks the stream handle so it can push messages to that specific user later.

The Fan-Out Problem

When one user posts to a room, the server must deliver it to every other member's stream. This fan-out is the heart of chat scaling.

In-Process Hub

A simple design keeps a hub mapping rooms to subscriber channels. Posting iterates members and sends to each.

func (h *Hub) Broadcast(room string, msg *ServerEvent) {
  for _, sub := range h.rooms[room] {
    sub.outbox <- msg
  }
}

Scaling Past One Instance

Users on different server instances must still see each other. Introduce a message bus (Redis Pub/Sub, NATS, Kafka) so instances relay messages to one another.

Cross-Instance Flow

An instance publishes new messages to the bus; every instance subscribes and forwards to its own local connections. This decouples delivery from where users connect.

Presence and Typing

Presence (online/offline) and typing indicators are just more event types on the stream. Track last-seen timestamps and broadcast presence changes via the same fan-out path.

Backpressure per Client

A slow client must not stall the hub. Give each session a bounded outbox; if it overflows, drop or disconnect that client instead of blocking everyone.

select {
case sub.outbox <- msg:
default:
  disconnect(sub) // slow consumer
}

Reconnection and Delivery

Networks drop. Clients reconnect and resume from a last-seen message id. Persist recent history so missed messages can be replayed on reconnect.

Operational Concerns

Production chat needs:

Keepalive to detect dead connections
Authentication on connect (token in metadata)
Metrics on active streams and fan-out latency
Graceful drain on deploy

Quick Check

Test your chat-design knowledge.

Recap

You designed a real-time chat backend:

Bidirectional streaming models each user session
A hub fans out room messages to subscribers
A message bus relays across multiple instances
Presence/typing are extra event types; per-client backpressure protects the hub
Reconnection replays missed messages; ops needs keepalive, auth, metrics, drain

常见问题解答

「使用 gRPC 设计实时聊天后端」课时是免费的吗？

是的 — 「使用 gRPC 设计实时聊天后端」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 gRPC & High Performance APIs 课程的其余内容，请升级到 CoddyKit PRO。 gRPC & High Performance APIs 课程共包含 4 节课。

「使用 gRPC 设计实时聊天后端」这节课中我会学到什么？

通过真实案例学习：使用 gRPC 双向流、扇出和在线状态，构建可扩展的实时聊天后端架构。你通过在浏览器中直接运行的动手代码来练习 gRPC & High Performance APIs，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 gRPC & High Performance APIs 需要有经验吗？

无需任何先前经验。CoddyKit 上的 gRPC & High Performance APIs 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 4 节课，共 4 节。

「使用 gRPC 设计实时聊天后端」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 gRPC & High Performance APIs 课中编写并运行代码吗？

能。每节 gRPC & High Performance APIs 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 gRPC & High Performance APIs