Skill-Profil

DDD Strategic Patterns

Bounded Contexts, Context Mapping, Ubiquitous Language, Anti-corruption Layer

Architecture & System Design Domain-Driven Design

Rollen

2

wo dieser Skill vorkommt

Stufen

4

strukturierter Entwicklungspfad

Pflichtanforderungen

6

die anderen 1 optional

Architecture & System Design

Domain-Driven Design

17.3.2026

Wählen Sie Ihr aktuelles Level und vergleichen Sie die Erwartungen.

Was wird auf jedem Level erwartet

Die Tabelle zeigt, wie die Tiefe von Junior bis Principal wächst.

Rolle	Pflicht	Beschreibung
Technical Lead		Applies DDD Strategic Patterns when designing components. Understands trade-offs. Participates in architectural discussions.

Rolle	Pflicht	Beschreibung
Solutions Architect	Pflicht	Designs bounded context maps aligned with business domains and team topology. Makes ADRs for context integration patterns (ACL, Open Host, Shared Kernel). Evaluates trade-offs between autonomy and consistency across context boundaries.
Technical Lead	Pflicht	Applies Context Mapping to decompose monoliths into cohesive microservices. Makes architectural decisions on Ubiquitous Language enforcement within team boundaries. Evaluates domain events as integration contracts between upstream and downstream contexts.

Rolle	Pflicht	Beschreibung
Solutions Architect	Pflicht	Defines product architectural strategy with DDD Strategic Patterns. Establishes architecture guidelines. Conducts architecture reviews.
Technical Lead	Pflicht	Defines the product's architectural strategy with DDD Strategic Patterns. Establishes architecture guidelines. Conducts architecture reviews.

Rolle	Pflicht	Beschreibung
Solutions Architect	Pflicht	Defines enterprise domain decomposition strategy across product lines and business units. Designs reference architectures for inter-domain communication using federated bounded contexts. Establishes governance for strategic pattern selection and context ownership models.
Technical Lead	Pflicht	Defines the organization's DDD adoption roadmap from legacy systems to strategic domain models. Designs reference architectures for event-driven context integration at scale. Establishes governance for bounded context lifecycle, team alignment, and cross-domain contracts.

Middle 1 Anforderungen

Technical Lead

Applies DDD Strategic Patterns when designing components. Understands trade-offs. Participates in architectural discussions.

Senior 2 Anforderungen

Solutions Architect
Pflicht

Designs bounded context maps aligned with business domains and team topology. Makes ADRs for context integration patterns (ACL, Open Host, Shared Kernel). Evaluates trade-offs between autonomy and consistency across context boundaries.
Technical Lead
Pflicht

Applies Context Mapping to decompose monoliths into cohesive microservices. Makes architectural decisions on Ubiquitous Language enforcement within team boundaries. Evaluates domain events as integration contracts between upstream and downstream contexts.

Lead / Staff 2 Anforderungen

Solutions Architect
Pflicht

Defines product architectural strategy with DDD Strategic Patterns. Establishes architecture guidelines. Conducts architecture reviews.
Technical Lead
Pflicht

Defines the product's architectural strategy with DDD Strategic Patterns. Establishes architecture guidelines. Conducts architecture reviews.

Principal 2 Anforderungen

Solutions Architect
Pflicht

Defines enterprise domain decomposition strategy across product lines and business units. Designs reference architectures for inter-domain communication using federated bounded contexts. Establishes governance for strategic pattern selection and context ownership models.
Technical Lead
Pflicht

Defines the organization's DDD adoption roadmap from legacy systems to strategic domain models. Designs reference architectures for event-driven context integration at scale. Establishes governance for bounded context lifecycle, team alignment, and cross-domain contracts.

Kommentare werden geladen...