domains / families / software-engineering / ddd-context-mapping

ddd-context-mapping

authentic

Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.

When to use

• 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.

When not to use

• You have a single-context system with no integrations.
• You only need internal class design.
• You are selecting cloud infrastructure tooling.
• 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.

Skill page

Source