From a1d24cb70ecb200041ce16a291198b3dda7f7b45 Mon Sep 17 00:00:00 2001 From: ralphmalph62 Date: Fri, 13 Feb 2026 10:09:44 -0500 Subject: [PATCH] Update Architecture.md --- docs/en/introduction/Architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/introduction/Architecture.md b/docs/en/introduction/Architecture.md index e111ac9a..ee370b67 100644 --- a/docs/en/introduction/Architecture.md +++ b/docs/en/introduction/Architecture.md @@ -3,7 +3,7 @@ import QSOverview from '../_assets/commonMarkdown/quickstart-overview-tip.mdx' # Architecture -OK +Edit by non-starrocks account StarRocks has a powerful architecture. The entire system consists of only two types of components: "frontends" and "backends". Frontend nodes are called **FE**. Backend nodes are divided into two types: **BE** and **CN** (compute node). When data uses local storage, BEs are deployed; when data is stored on object storage or HDFS, CNs are deployed. StarRocks does not rely on any external components, which simplifies deployment and maintenance. Nodes can be scaled horizontally without downtime. In addition, StarRocks has a replica mechanism for metadata and service data, which improves data reliability and effectively prevents single points of failure (SPOFs).