Relationship(s) between problem and solution space

One of the more confusing concepts in Domain-Driven Desing is that of problem and solution space. There has been a long debate on Twitter and the ddd-crew github:

People wonder how distilling the Core with the Core, supportive and generic subdomains fit and what space. What concepts are in the problem space, and what is the solution? And what is a precise definition of problem and solution space?

Join us in this session are a diverse group of people spanning multiple disciplines to look at how they see the relationship(s) between problem and solution space in IT. And hopefully, in the end, we can have a useful, consistent model of those relationships between problem and solution space, core, supportive, generics (sub)domains for the #DDDesign community. With us will be: Dawn N Ahukanna Jabe Bloom Indi Young Nick Tune



Follow us

Read our latest news from Virtual DDD on any of these social networks!

Latest sessions

Splitting systems towards bounded contexts and microservices

Splitting systems towards bounded contexts and microservices

There are many reasons to split up large-scale systems towards more modular, smaller services with their own model and language. You can decouple teams and give full autonomy of that service to a team. By decoupling services and teams you can handle changes to the...