请求面、主控与数据面相互独立 Request, control and data planes — kept separate
主控负责统一编排和配置下发，边缘节点独立承载业务请求。即使节点与主控暂时断连，也可继续使用本地缓存配置提供服务；运行日志则单独汇入日志分析数据面。以下展示三类平面的职责划分及组件关系。 The control plane orchestrates and distributes config, while edge nodes serve requests on their own — and keep serving from locally cached config even when briefly disconnected. Operational logs flow into a separate log-analytics data plane. Below is how the three planes divide responsibility and how the components relate.
三类平面的职责与数据流How the three planes divide responsibility and route data
主控负责统一编排和配置下发，边缘节点独立承载业务请求。即使节点与主控暂时断连，也可继续使用本地缓存配置提供服务；运行日志则单独汇入日志分析数据面。The control plane orchestrates and distributes config, while edge nodes serve requests on their own — and keep serving from locally cached config even when briefly disconnected. Operational logs flow into a separate log-analytics data plane.
主控、Agent、节点与日志系统如何协同How the control plane, agent, nodes and logs work together
以下内容描述各组件在架构中的职责：由谁统一编排、由谁承载流量、断连时如何继续服务、配置和升级如何下发，以及日志最终写入何处。这里仅说明高层架构，不代表具体的网络拓扑或传输配置。The following describes each component's role in the architecture: who orchestrates, who carries traffic, how service continues through disconnection, how config and upgrades are pushed, and where logs finally land. This is a high-level view only — not a statement of specific network topology or transport configuration.
主控 API 与授权服务Master API & license server
主控 API 通过 REST 和 gRPC 编排全局配置；授权服务结合签名授权文件与在线心跳，校验授权版本以及节点数、Zone 数配额。The Master API orchestrates global config over REST and gRPC; the license server combines a signed license file with an online heartbeat to validate the edition and the node and Zone quotas.
边缘节点与 cdn-agentEdge nodes & cdn-agent
每台主机常驻一个 cdn-agent，通过双向 gRPC 心跳与主控同步状态。配置经 gRPC Watch 增量下发，节点会将最新配置持久化到本地。A cdn-agent runs on every host and syncs state with the control plane over a bidirectional gRPC heartbeat. Config is pushed incrementally over gRPC Watch, and nodes persist the latest config locally.
回源中继（可选）Origin relay (optional)
回源中继位于边缘节点与源站之间，可用于跨网络回源，也可作为备用回源链路，按实际需要部署。The origin relay sits between edge nodes and origins; it can be used for cross-network origin pulls or as a backup origin route, deployed as needed.
主控断连时继续服务Serving when the control plane is unreachable
主控暂时不可达时，边缘节点会继续使用最近一次持久化的有效配置处理请求，避免请求面因主控波动而中断。When the control plane is temporarily unreachable, edge nodes keep handling requests with the last persisted valid config, so control-plane fluctuations don't stall the request plane.
签名升级Signed upgrades
cdn-agent 下载升级包后，会校验 SHA-256 摘要与 Ed25519 签名，随后执行原子替换并重启，避免加载被篡改的二进制文件。After downloading an upgrade package, cdn-agent verifies its SHA-256 digest and Ed25519 signature, then atomically replaces and restarts — avoiding any tampered binary.
日志分析数据面Log-analytics data plane
边缘节点和回源中继产生的日志，经 Log Ingestor 完成 HMAC 鉴权和批量写入后，可汇入外置 ClickHouse，用于访问、回源和高可用分析。ClickHouse 为可选组件。Logs from edge nodes and origin relays pass through a Log Ingestor (HMAC auth, batch write) and can flow into an external ClickHouse for access, origin-pull and HA analytics. ClickHouse is an optional component.
把 CDN 的控制权掌握在自己手中Keep full control of your CDN
按节点数和授权站点数（以根域名 Zone 计）透明计费，可根据实际部署规模选择合适的授权档位。Transparent pricing by node count and licensed-site count (counted per root-domain Zone) — choose the licensing tier that matches your deployment.