六边形（端口与适配器）架构

Architecture

六边形架构图，展示领域核心、入站适配器（REST、GraphQL、CLI、消息消费者）、出站适配器（PostgreSQL、Stripe、邮件、Redis）以及连接它们的端口接口之间的清晰分离。该模板可视化端口与适配器模式，领域核心对基础设施零依赖，使其完全可测试且技术无关。对于在代码库中采用整洁架构原则的团队至关重要。

下载 .fz 文件

完整 FlowZap 代码

InboundAdapters { # Inbound Adapters (Driving)
n1: rectangle label:"REST Controller"
n2: rectangle label:"GraphQL Resolver"
n3: rectangle label:"CLI Command Handler"
n4: rectangle label:"Message Consumer"
n1.handle(bottom) -> Ports.n5.handle(top) [label="Port: CreateOrder"]
n2.handle(bottom) -> Ports.n5.handle(top) [label="Port: CreateOrder"]
n3.handle(bottom) -> Ports.n6.handle(top) [label="Port: RunReport"]
n4.handle(bottom) -> Ports.n6.handle(top) [label="Port: ProcessEvent"]
}
Ports { # Ports (Interfaces)
n5: rectangle label:"Inbound Port: OrderUseCase"
n6: rectangle label:"Inbound Port: ReportUseCase"
n7: rectangle label:"Outbound Port: OrderRepository"
n8: rectangle label:"Outbound Port: PaymentGateway"
n5.handle(bottom) -> Core.n9.handle(top) [label="Implement"]
n6.handle(bottom) -> Core.n10.handle(top) [label="Implement"]
}
Core { # Domain Core (Hexagon)
n9: rectangle label:"Order Service"
n10: rectangle label:"Report Service"
n11: rectangle label:"Domain Model (Entities)"
n12: rectangle label:"Business Rules (Value Objects)"
n9.handle(right) -> n11.handle(left) [label="Use"]
n10.handle(right) -> n11.handle(left) [label="Use"]
n11.handle(right) -> n12.handle(left) [label="Enforce"]
n9.handle(bottom) -> Ports.n7.handle(top) [label="Call Port"]
n9.handle(bottom) -> Ports.n8.handle(top) [label="Call Port"]
}
OutboundAdapters { # Outbound Adapters (Driven)
n13: rectangle label:"PostgreSQL Repository"
n14: rectangle label:"Stripe Payment Adapter"
n15: rectangle label:"Email Notification Adapter"
n16: rectangle label:"Redis Cache Adapter"
n7.handle(bottom) -> OutboundAdapters.n13.handle(top) [label="Implements"]
n8.handle(bottom) -> OutboundAdapters.n14.handle(top) [label="Implements"]
n13.handle(right) -> n15.handle(left)
n14.handle(right) -> n16.handle(left)
}

为什么需要这个工作流？

When business logic depends directly on frameworks, databases, and external services, it becomes impossible to test in isolation and expensive to change infrastructure. Hexagonal architecture inverts these dependencies through ports (interfaces) and adapters (implementations), keeping the domain core pure and technology-agnostic.

工作原理

Step 1: Inbound adapters (REST controllers, GraphQL resolvers, CLI handlers) receive external input.
Step 2: Adapters call inbound port interfaces defined by the domain core.
Step 3: The domain core implements business logic using entities and value objects.
Step 4: When the domain needs infrastructure, it calls outbound port interfaces.
Step 5: Outbound adapters (PostgreSQL repository, Stripe payment, email sender) implement these ports.
Step 6: Swapping infrastructure requires only changing the adapter, not the domain code.

替代方案

Layered architecture is simpler but allows infrastructure dependencies to leak into business logic. Clean Architecture adds more layers but follows the same dependency inversion principle. This template shows the hexagonal approach with concrete adapter examples.

Key Facts

Template Name	六边形（端口与适配器）架构
Category	Architecture
Steps	6 workflow steps
Format	FlowZap Code (.fz file)