Perfil de habilidad

DDD Strategic Patterns

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

Architecture & System Design Domain-Driven Design

Roles

2

donde aparece esta habilidad

Niveles

4

ruta de crecimiento estructurada

Requisitos obligatorios

6

los otros 1 opcionales

Architecture & System Design

Domain-Driven Design

17/3/2026

Selecciona tu nivel actual y compara las expectativas.

Qué se espera en cada nivel

La tabla muestra cómo crece la profundidad desde Junior hasta Principal.

Rol	Obligatorio	Descripción
Technical Lead		Applies DDD Strategic Patterns when designing components. Understands trade-offs. Participates in architectural discussions.

Rol	Obligatorio	Descripción
Solutions Architect	Obligatorio	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	Obligatorio	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.

Rol	Obligatorio	Descripción
Solutions Architect	Obligatorio	Defines product architectural strategy with DDD Strategic Patterns. Establishes architecture guidelines. Conducts architecture reviews.
Technical Lead	Obligatorio	Defines the product's architectural strategy with DDD Strategic Patterns. Establishes architecture guidelines. Conducts architecture reviews.

Rol	Obligatorio	Descripción
Solutions Architect	Obligatorio	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	Obligatorio	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 requisitos

Technical Lead

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

Senior 2 requisitos

Solutions Architect
Obligatorio

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
Obligatorio

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 requisitos

Solutions Architect
Obligatorio

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

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

Principal 2 requisitos

Solutions Architect
Obligatorio

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
Obligatorio

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.

Cargando comentarios...