by Organisers @virtualddd | Jul 22, 2024
Short description Group things that frequently change together to avoid coupling across boundaries. Examples For instance a payment service, or a user profile service or an notification service. Context We should align boundaries in sociotechnical systems with our...
by Organisers @virtualddd | Jul 22, 2024
Short description align boundaries with the people asking for changes because those people will care about concepts which are likely to be more closely related. Examples separate business-to-business and business-to-consumer services because both customer segments...
by Organisers @virtualddd | Jul 22, 2024
Short description align boundaries with data which must always be immediately consistent. Examples When a user reserve specific seats for a cinema those seats needs to stay reserved and unavailable for other users for a certain amount of time while the user pays....
by Organisers @virtualddd | Jul 22, 2024
Short description Look for parts of the domain which have not changed in a long time. Sometimes dependencies are so generic that you don't want to invest time in it and you want to buy them of the shelf: see [outsourced-generic-subdomains](Outsource generic...
by Organisers @virtualddd | Jul 22, 2024
Short description From a process or design level EventStorming, design your bounded contexts around the purple sticky called a policy. Examples When a domain experts mentions: When this event happens we will start the reservation process. We can add a policy that can...
