This is an automated email from the ASF dual-hosted git repository.
shenghang pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/seatunnel.git
The following commit(s) were added to refs/heads/dev by this push:
new f8414ce569 [Improve] [Docs] Polish architecture descriptions and avoid
file name ambiguities (#10550)
f8414ce569 is described below
commit f8414ce569d2850bb9ede290be8e0bc66b176e1a
Author: David Zollo <[email protected]>
AuthorDate: Mon Mar 2 14:23:30 2026 +0800
[Improve] [Docs] Polish architecture descriptions and avoid file name
ambiguities (#10550)
Co-authored-by: github-actions[bot]
<github-actions[bot]@users.noreply.github.com>
---
docs/en/architecture/overview.md | 4 ++--
docs/en/introduction/about.md | 6 ++----
docs/en/introduction/{architecture.md => how-it-works.md} | 4 ++--
docs/sidebars.js | 4 ++--
docs/zh/architecture/overview.md | 4 ++--
docs/zh/introduction/about.md | 6 +++---
docs/zh/introduction/{architecture.md => how-it-works.md} | 4 ++--
7 files changed, 15 insertions(+), 17 deletions(-)
diff --git a/docs/en/architecture/overview.md b/docs/en/architecture/overview.md
index 53fc699637..ab5ae823c7 100644
--- a/docs/en/architecture/overview.md
+++ b/docs/en/architecture/overview.md
@@ -9,10 +9,10 @@ title: Architecture Overview
### 1.1 Design Goals
-SeaTunnel is designed as a distributed data integration platform with the
following core objectives:
+SeaTunnel is designed as a distributed multimodal data integration tool with
the following core objectives:
- **Engine Independence**: Decouple connector logic from execution engines,
enabling the same connectors to run on SeaTunnel Engine (Zeta), Apache Flink,
or Apache Spark
-- **High Performance**: Support large-scale data synchronization with high
throughput and low latency
+- **High Performance**: Support large-scale data synchronization with
ultra-high-performance throughput and low latency
- **Fault Tolerance**: Provide exactly-once semantics through distributed
snapshots and two-phase commit
- **Ease of Use**: Offer simple configuration and a rich connector ecosystem
- **Extensibility**: Plugin-based architecture allowing easy addition of new
connectors and transforms
diff --git a/docs/en/introduction/about.md b/docs/en/introduction/about.md
index 33ba67ce7e..50a24d71bf 100644
--- a/docs/en/introduction/about.md
+++ b/docs/en/introduction/about.md
@@ -5,9 +5,7 @@
[](https://s.apache.org/seatunnel-slack)
[](https://x.com/ASFSeaTunnel)
-SeaTunnel is a very easy-to-use, multimodal, ultra-high-performance,
distributed data integration platform that supports real-time
-synchronization of massive data. It can synchronize tens of billions of data
stably and efficiently every day, and has
-been used in production by nearly 100 companies.
+SeaTunnel is a multimodal, ultra-high-performance, distributed data
integration tool, capable of synchronizing vast amounts of data daily. It's
trusted by numerous companies for its efficiency and stability.
## Why We Need SeaTunnel
@@ -43,7 +41,7 @@ The user configures the job information and selects the
execution engine to subm
The Source Connector is responsible for parallel reading and sending the data
to the downstream Transform or directly to the Sink, and the Sink writes the
data to the destination. It is worth noting that Source, Transform and Sink can
be easily developed and extended by yourself.
-SeaTunnel is an EL(T) data integration platform. Therefore, in SeaTunnel,
Transform can only be used to perform some simple transformations on data, such
as converting the data of a column to uppercase or lowercase, changing the
column name, or splitting a column into multiple columns.
+SeaTunnel is an EtL(T) data integration tool. Therefore, in SeaTunnel,
transform can only be used to perform some simple transformations on data, such
as converting the data of a column to uppercase or lowercase, changing the
column name, or splitting a column into multiple columns.
The default engine use by SeaTunnel is [SeaTunnel
Engine](../engines/zeta/about.md). If you choose to use the Flink or Spark
engine, SeaTunnel will package the Connector into a Flink or Spark program and
submit it to Flink or Spark to run.
diff --git a/docs/en/introduction/architecture.md
b/docs/en/introduction/how-it-works.md
similarity index 95%
rename from docs/en/introduction/architecture.md
rename to docs/en/introduction/how-it-works.md
index 671c302b78..625ca6c1f7 100644
--- a/docs/en/introduction/architecture.md
+++ b/docs/en/introduction/how-it-works.md
@@ -2,11 +2,11 @@
sidebar_position: 2
---
-# Architecture
+# How it works
## Overview
-SeaTunnel is a distributed data integration platform with a pluggable
architecture. It decouples the connector layer from the execution engine,
allowing the same connectors to run on different engines.
+SeaTunnel is a distributed multimodal data integration tool with a pluggable
architecture. It decouples the connector layer from the execution engine,
allowing the same connectors to run on different engines.
```
┌─────────────────────────────────────────────────────────────┐
diff --git a/docs/sidebars.js b/docs/sidebars.js
index f839fb5429..4f56265ec2 100644
--- a/docs/sidebars.js
+++ b/docs/sidebars.js
@@ -25,7 +25,7 @@ const sidebars = {
"label": "Introduction",
"items": [
"introduction/about",
- "introduction/architecture",
+ "introduction/how-it-works",
{
"type": "category",
"label": "Concepts",
@@ -222,7 +222,7 @@ const sidebars = {
"image": "/img/favicon.ico"
},
"items": [
- {
+ {
"type": "category",
"label": "Common Options",
"items": [
diff --git a/docs/zh/architecture/overview.md b/docs/zh/architecture/overview.md
index 44a4bbc8cb..8729b7cabd 100644
--- a/docs/zh/architecture/overview.md
+++ b/docs/zh/architecture/overview.md
@@ -9,10 +9,10 @@ title: 架构概览
### 1.1 设计目标
-SeaTunnel 设计为分布式数据集成平台，具有以下核心目标：
+SeaTunnel 设计为分布式多模态数据集成工具，具有以下核心目标：
- **引擎独立性**：将连接器逻辑尽量与执行引擎解耦；连接器可通过转换层适配到不同引擎，具体可用性以连接器能力与引擎支持为准
-- **高性能**：支持高吞吐、低延迟的大规模数据同步
+- **超高性能**：支持高吞吐、低延迟的大规模数据同步
- **容错性**：在启用 checkpoint 且外部系统支持事务/幂等提交等前提下，通过分布式快照与提交协议提供可验证的一致性语义
- **易用性**：提供简单的配置方式和丰富的连接器生态系统
- **可扩展性**：基于插件的架构，便于添加新的连接器和转换组件
diff --git a/docs/zh/introduction/about.md b/docs/zh/introduction/about.md
index 855c56730d..7cc4f022de 100644
--- a/docs/zh/introduction/about.md
+++ b/docs/zh/introduction/about.md
@@ -5,7 +5,7 @@
[](https://s.apache.org/seatunnel-slack)
[](https://x.com/ASFSeaTunnel)
-SeaTunnel是一个非常易用、多模态、超高性能的分布式数据集成平台，支持实时海量数据同步。 每天可稳定高效同步数百亿数据，已被近百家企业应用于生产。
+SeaTunnel是一个多模态、超高性能、分布式的海量数据集成工具，每天可稳定高效同步数百亿数据，已被数千家企业应用于生产，以其高效和稳定性深受众多企业信赖。
## 为什么需要 SeaTunnel
@@ -41,9 +41,9 @@ SeaTunnel的运行流程如上图所示。
Source Connector负责并行读取数据并将数据发送到下游Transform或直接发送到Sink，Sink将数据写入目的地。
值得注意的是，Source、Transform 和 Sink 可以很容易地自行开发和扩展。
-SeaTunnel 是一个 EL(T) 数据集成平台。
因此，在SeaTunnel中，Transform只能用于对数据进行一些简单的转换，例如将一列的数据转换为大写或小写，更改列名，或者将一列拆分为多列。
+SeaTunnel 是一个 EtL(T) 数据集成工具。
因此，在SeaTunnel中，transform(t)只能用于对数据进行一些简单的转换，例如将一列的数据转换为大写或小写，更改列名，或者将一列拆分为多列。
-SeaTunnel 使用的默认引擎是 [SeaTunnel Engine](../engines/zeta/about.md)。
如果您选择使用Flink或Spark引擎，SeaTunnel会将Connector打包成Flink或Spark程序并提交给Flink或Spark运行。
+SeaTunnel 使用的默认引擎是 [SeaTunnel Zeta Engine](../engines/zeta/about.md)。
如果您选择使用Flink或Spark引擎，SeaTunnel会将Connector打包成Flink或Spark程序并提交给Flink或Spark运行。
## 连接器
diff --git a/docs/zh/introduction/architecture.md
b/docs/zh/introduction/how-it-works.md
similarity index 96%
rename from docs/zh/introduction/architecture.md
rename to docs/zh/introduction/how-it-works.md
index 55a59fc77c..dd1e8cc0cf 100644
--- a/docs/zh/introduction/architecture.md
+++ b/docs/zh/introduction/how-it-works.md
@@ -2,11 +2,11 @@
sidebar_position: 2
---
-# 架构设计
+# 工作原理
## 概述
-SeaTunnel 是一个分布式数据集成平台，采用插件化架构。连接器层与执行引擎解耦，同一套连接器可在不同引擎上运行。
+SeaTunnel 是一个分布式多模态数据集成工具，采用插件化架构。连接器层与执行引擎解耦，同一套连接器可在不同引擎上运行。
```
┌─────────────────────────────────────────────────────────────┐
