integrating bounded contexts - mini-workshop
TRANSCRIPT
INTEGRATING BOUNDED CONTEXTSMini-workshop
THE DOMAIN == THE PROBLEM SPACE
➤ Domain is divided into subdomains:
➤ Core domain
➤ Supporting subdomain(s)
➤ Generic subdomain(s)
BOUNDED CONTEXTS == THE SOLUTION SPACE
➤ Think “application” instead
➤ Ideally, a bounded context models no more than one subdomain
subdomain
bounded context
ORGANIZATIONAL & INTEGRATION PATTERNS
PARTNERSHIP
➤ Succeed or fail together.
SHARED KERNEL
➤ Share part of the model.
CUSTOMER-SUPPLIER
➤ Upstream-downstream relationship.
CONFORMIST
➤ Same as customer-development, but without cooperation.
ANTICORRUPTION LAYER
➤ Provide functionality of the upstream system in terms of your own model.
OPEN HOST SERVICE
➤ There is a (generic) service which can be used by other bounded contexts.
PUBLISHED LANGUAGE
➤ A well-documented, shared language, to allow for translation between models from different contexts.
SEPARATE WAYS
➤ A bounded context has no relation with other contexts.
BIG BALL OF MUD
➤ When models aren’t clearly separated by context boundaries.
