CODEWITHSUNDEEP
domain-driven-designaggregaterootbounded-contexts
Laoujin
Laoujin

Reputation: 10229

DDD - How to design associations between different bounded contexts

I have setup a domain project which is being populated with an ORM. The domain contains of different aggregates each with its own root object. My question is how properties that cross the aggregate boundries should be treated?

An example:
Context A = Users
Context B = Games

Inside the Users context there is an object UserOwnedGames. This object has a property User which is a reference to an object in the same Users context. The object also has a property to a Game which is obviously not in the Users but rather in the Games context.

How would (or should?) this relation look like? It's clear in the database (ie 2 foreign keys) but what should the code look like?

Upvotes: 12

Views: 6346

Answers (4)

Jhon Zambrano
Jhon Zambrano

Reputation: 31

You must think about BCs as logical separations, they are referred to how people are grouped and existent relationships between each team. Said that, you can maybe consider to keep User and Games in a single bounded context keeping together what must be together. Please refer to this amazing video Hiden lessons from the big blue book

Upvotes: 0

MattDavey
MattDavey

Reputation: 9017

It sounds like your User context also needs a Game entity. Note however that this is not necessarily the same Game entity which is the root of the Game context. These two bounded contexts may have different ideas of what a Game is, and what properties it has. Only the identity ties the two Game objects together.

User Context
{
    Aggregate Root User
    {
        Identity;
        Name;
        OwnedGames : List of Game value entities
    }

    Value Entity Game
    {
        Identity;
        Name;
    }
}

Game Context
{
    Aggregate Root Game
    {
        Identity;
        Name;
        Owner : User value entity
        HighScore : int
        TimesPlayed : int
        ... A whole bunch of other properties which are not relevant in the User context
    }

    Value Entity User
    {
        Identity;
        Name;
        // No OwnedGames property, in this context we don't care about what other games the user owns.
    }
}

Upvotes: 19

gseric
gseric

Reputation: 649

You should avoid DB references across BCs - you shouldn't try to ensure referential integrity between aggregates from different BCs (transactions). Ideally, transaction should live only inside single aggregate, not even BC.

Better use simple value objects for IDs - UserId and GameId - and assign them to entity if needed. This way those "remote" entities are completely detached so you don't have to worry about their connection. Sync could be implemented using messaging platform.

If you have spare time read these valuable articles (by Vaughn Vernon):

Upvotes: 4

Yugang Zhou
Yugang Zhou

Reputation: 7283

It depends on what bounded context strategy you use.

If you choose shared kernal, I think it's fine to have a direct relationship between them(direct reference or identifier reference, I believe someone else will explain the pros and cons in other answers). and you've also mentioned these objects integrated by database tables.

But if you choose anti-corruption-layer, you'd better seperate them(use just identifier to keep the relationship), use adapter-translator to integrate(and no database integration).

Upvotes: 3

Related Questions