Presentations
Templates
Features
Teams
Pricing
Log in
Sign up
Log in
Sign up
Menu
DOMAIN-DRIVEN DESIGN
Context maps
DOMAIN-DRIVEN DESIGN
learned so far
CORE DOMAIN
drives the main business value to the system
SUB-DOMAINS
are responsible for a single business unit
Domain Models
smallest programming unit, part of sub-domains
Bounded Context
ubiquitous language isolation, containing multiple sub-domains
DOMAIN-DRIVEN DESIGN
CONTEXT MAPS
overview
Visual description of
relationships between
Bounded Context
Description and insight of
inter-team
relationship and communication catalyst
Inventory of systems
to interact to and interaction type
Adds value in
high-level architectural
investigations
DOMAIN-DRIVEN DESIGN
organizational
patterns
Partnership
both teams will succeed or fail together; same release
Shared Kernel
when team share same context; same UL; close
inter-dependency
Conformist
when downstream team needs are second by the upstream's priorities
DOMAIN-DRIVEN DESIGN
integration patterns
Customer-Supplier Development
when using Up/Down - stream approach
Open Host Service
when using an open protocol to access the system
Anti-corruption
Layer
when using an interface to isolate a downstream system
DOMAIN-DRIVEN DESIGN
INTEGRATION ANTI-PATTERNS
Separate Ways
when using isolated, highly specialized
solutions
Big Ball of Mud
when models are
mixed
and boundaries are inconsistent
Resume presentation
DOMAIN-DRIVEN DESIGN Context maps
Domain-Driven Design - Context Maps
By dragoshont
Made with Slides.com
Domain-Driven Design - Context Maps
11 years ago
860
dragoshont
More from
dragoshont
BESbswy
BESbswy
BESbswy
BESbswy
