Uploaded January 2018 | Updated September 2026, 2 weeks ago
Domain-driven design grew in popularity during the last decade and we see more and more people coming to our community, seeking for answers and are eager to share their experiences. But more often than not we hear stories of failures. People keep saying that they have tried domain-driven design and it did not really work. When we dig deeper into the issues, we often discover things like "we used Entity Framework and repositories and this was our biggest issue". Clearly, this is not the DDD you're looking for. This talk is targeted for people who struggled with that sort of issues or have heard similar stories and are now unsure about starting with DDD. We will explore the essence of domain-driven design and why ORMs have nothing to do with it.
Domain-driven design grew in popularity during the last decade and we see more and more people coming to our community, seeking for answers and are eager to share their experiences. But more often than not we hear stories of failures. People keep saying that they have tried domain-driven design and it did not really work. When we dig deeper into the issues, we often discover things like "we used Entity Framework and repositories and this was our biggest issue". Clearly, this is not the DDD you're looking for. This talk is targeted for people who struggled with that sort of issues or have heard similar stories and are now unsure about starting with DDD. We will explore the essence of domain-driven design and why ORMs have nothing to do with it.
