How DDD fits with Solution Space

In solution space domain driven design suggests us to

i. Identify the bounded contexts within each subdomain based on nature of work / context and ubiquitous language
ii. Map the between bounded contexts based on the nature of their communication with each other
iii. Convert the mental model into Domain model using patterns like Entity, Value Object, Aggregate,
Factory, Domain Event etc.
iV. Use Repository for mediate between Domain Model and Data Access
V. Use Domain Service for call third party services, API’s etc.
Vi. When any logic relies into more than one models then use Domain Service to coordinate those domain models to
implement that logic
Vi. Use application service when any external consumers needs to consume any service then expose that service
from here
Vi. Use infrastructure service when any abstract technical concerns like email service or MSMQ or RabbitMQ
or such type of services needs to use by the system

i Generic
Bounded Subdomain
Supporting Context7
Bounded Subdomain ii
ii
Context1
ii Bounded
i i Context6
Use to Bounded
Ubiquitouse Language Context2 ii
i ii
Bounded i
Context3
ii Bounded
Context5 Generic
i Subdomain
ii ii
ii Bounded
Bounded Context4
ii
Context i
i
Core Subdomain

i Identify the bounded contexts within each subdomain based on nature of work and ubiquitous language
ii Map the between bounded contexts based on the nature of their communication with each other