Back to Details

ddd-context-mapping

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

DDD Context Mapping

DDD上下文映射

Use this skill when

适用场景

  • Defining integration patterns between bounded contexts.
  • Preventing domain leakage across service boundaries.
  • Planning anti-corruption layers during migration.
  • Clarifying upstream and downstream ownership for contracts.
  • 定义限界上下文之间的集成模式。
  • 防止领域逻辑跨服务边界泄露。
  • 在迁移过程中规划Anti-corruption layers。
  • 明确契约的上游和下游归属。

Do not use this skill when

不适用场景

  • You have a single-context system with no integrations.
  • You only need internal class design.
  • You are selecting cloud infrastructure tooling.
  • 你拥有无集成的单上下文系统。
  • 仅需进行内部类设计。
  • 正在选择云基础设施工具。

Instructions

操作步骤

  1. List all context pairs and dependency direction.
  2. Choose relationship patterns per pair.
  3. Define translation rules and ownership boundaries.
  4. Add failure modes, fallback behavior, and versioning policy.
If detailed mapping structures are needed, open 
references/context-map-patterns.md
.
  1. 列出所有上下文对及依赖方向。
  2. 为每对上下文选择关系模式。
  3. 定义转换规则和归属边界。
  4. 添加故障模式、回退行为和版本控制策略。
如果需要详细的映射结构，请打开
references/context-map-patterns.md
。

Output requirements

输出要求

  • Relationship map for all context pairs
  • Contract ownership matrix
  • Translation and anti-corruption decisions
  • Known coupling risks and mitigation plan
  • 所有上下文对的关系映射图
  • 契约归属矩阵
  • 转换与防腐层决策
  • 已知耦合风险及缓解方案

Examples

示例

text
Use @ddd-context-mapping to define how Checkout integrates with Billing,
Inventory, and Fraud contexts, including ACL and contract ownership.
text
使用@ddd-context-mapping定义Checkout上下文如何与Billing、Inventory和Fraud上下文集成，包括ACL和契约归属。

Limitations

局限性

  • This skill does not replace API-level schema design.
  • It does not guarantee organizational alignment by itself.
  • It should be revisited when team ownership changes.
  • 该技能无法替代API级别的schema设计。
  • 它本身无法保证组织层面的对齐。
  • 当团队归属变更时，应重新审视该技能的应用。