Keep your domain model decoupled from frameworks

Short description The domain model is the core of our bounded context. When we implement the domain model we want the ability to keep this consistent with our ubiqituous language. We want the ability to quicly refactor this to represent our mind-model of our domain...

Optimise for future potential

Short description Even is sometime is core now, keep it as a seperate boundry anyway. Examples one option is to have a discovery context which have search catalog and recommendations. But if you know that one of those things is going to be a key part of the business...

Outsource generic subdomains

Short description Sometimes dependencies are so generic that you don't want to invest time in it and you can either buy them off the shelf or use a SaaS functionality. You only oursource when there is enough competition in that market Examples Payment providers...

Separate engagement and revenue

Short description When looking for boundries you can group things that make money and things that don't make money but provide some value to the user. Examples google has a search engine, but makes money out of ads. They don't get money from their users, but...