整洁架构层次

Architecture

整洁架构层次图，展示四个同心层：实体（领域）、用例（应用）、接口适配器（控制器、展示器、仓储）和框架与驱动（Web 服务器、数据库、云 SDK）。该模板模拟 Uncle Bob 的整洁架构及其依赖规则——内层永远不依赖外层，确保领域模型保持纯净且框架无关。对于强制架构边界的软件架构师来说是必备参考。

下载 .fz 文件

完整 FlowZap 代码

External { # External Layer (Frameworks & Drivers)
n1: rectangle label:"Express/Fastify Web Server"
n2: rectangle label:"PostgreSQL Driver"
n3: rectangle label:"Redis Client"
n4: rectangle label:"AWS SDK"
n1.handle(bottom) -> Interface.n5.handle(top) [label="HTTP Request"]
n2.handle(bottom) -> Interface.n8.handle(top) [label="DB Connection"]
n3.handle(bottom) -> Interface.n8.handle(top) [label="Cache"]
}
Interface { # Interface Adapters Layer
n5: rectangle label:"Controller"
n6: rectangle label:"Presenter"
n7: rectangle label:"DTO Mapper"
n8: rectangle label:"Repository Implementation"
n5.handle(right) -> n7.handle(left) [label="Map Input"]
n7.handle(bottom) -> UseCase.n9.handle(top) [label="Request Model"]
n6.handle(top) -> External.n1.handle(bottom) [label="View Model"]
n8.handle(bottom) -> UseCase.n12.handle(top) [label="Implements"]
}
UseCase { # Use Cases Layer (Application)
n9: rectangle label:"Create Order Use Case"
n10: rectangle label:"Get Order Use Case"
n11: rectangle label:"Cancel Order Use Case"
n12: rectangle label:"Order Repository Interface"
n9.handle(bottom) -> Entity.n13.handle(top) [label="Call Domain"]
n10.handle(bottom) -> Entity.n13.handle(top) [label="Query"]
n11.handle(bottom) -> Entity.n14.handle(top) [label="Cancel"]
n9.handle(right) -> n12.handle(left) [label="Persist"]
n10.handle(top) -> Interface.n6.handle(bottom) [label="Output"]
}
Entity { # Entities Layer (Domain)
n13: rectangle label:"Order Aggregate Root"
n14: rectangle label:"Order Item Entity"
n15: rectangle label:"Money Value Object"
n16: rectangle label:"Order Status Enum"
n13.handle(right) -> n14.handle(left) [label="Contains"]
n14.handle(right) -> n15.handle(left) [label="Uses"]
n13.handle(bottom) -> n16.handle(top) [label="State"]
}

为什么需要这个工作流？

Frameworks and databases change frequently, but business rules should remain stable. Clean Architecture enforces the dependency rule—inner layers never depend on outer layers—ensuring that the most important code (domain logic) is the most stable and testable, while infrastructure details are easily replaceable.

工作原理

Step 1: The Entities layer defines domain models, value objects, and business rules.
Step 2: The Use Cases layer implements application-specific business logic.
Step 3: The Interface Adapters layer converts data between use case format and external format.
Step 4: The Frameworks & Drivers layer contains web servers, database drivers, and cloud SDKs.
Step 5: Dependencies point inward: controllers depend on use cases, use cases depend on entities.
Step 6: The repository interface is defined in the use case layer but implemented in the adapter layer.

替代方案

Traditional MVC mixes concerns across layers. Hexagonal architecture is similar but uses different terminology. Vertical slice architecture organizes by feature instead of layer. This template provides the canonical Clean Architecture reference.

Key Facts

Template Name	整洁架构层次
Category	Architecture
Steps	6 workflow steps
Format	FlowZap Code (.fz file)