CODEWITHSUNDEEP
domain-driven-design
Micael Dias
Micael Dias

Reputation: 341

DDD Domain vs Aggregates

I'm trying to wrap my head around DDD.

Say we have a job board website where Organisations can post jobs and an Applicant can apply.

Is my understanding correct that, there would be a Recruitment domain with:

Recruitment
└── Model
    ├── Entities
    │   ├── Applicant
    │   └── HiringOrganisation
    │   └── Location
    ├── ValueObjects
    │   └── Salary
    │   └── EmploymentType
    ├── JobPost
    └── JobPostApplication

If so, how would:

Upvotes: 1

Views: 105

Answers (1)

VoiceOfUnreason
VoiceOfUnreason

Reputation: 57397

how would the Applicant relate to the User from the Auth domain the HiringOrganisation relate to the Organisation in the Organisations domain

Typically: shared identifiers. Some value (often an opaque token, like a UUID) is shared by both contexts, so that we can correlate messages that are talking about the "same" thing, in different spaces where the data evolves over time.

Upvotes: 2

Related Questions