Domain Driven Design is a vision and approach for dealing with highly complex domains that is based on making the domain itself the main focus of the project, and maintaining a software model that reflects a deep understanding of the domain. The vision was brought to the world by Eric Evans in his book "Domain Driven Design". Eric's work was based on 20 years of widely accepted best practices in the object community, as well as Eric's own insights. Included in the InfoQ minibook Domain-Driven Design Quickly, was an interview with Eric Evans, published separately as an article to get more viewership.
Read Eric Evans on why DDD Matters Today.
In the interview, Eric Evans puts DDD into modern context and explains why DDD is relevant today, how DDD fits into today's development platforms (Java, .NET, etc), and what's been new in the DDD world since 2003.
At the recent Spring Experience conference, InfoQ did a video interview with Eric which will appear on InfoQ in the coming months. One of the questions answered was what are the minimal practices required for one to say they are doing DDD? Eric responded that the two main ones are using the ubiquitous language, and also the bounded context pattern.
Read Eric Evans on why DDD Matters Today.
In the interview, Eric Evans puts DDD into modern context and explains why DDD is relevant today, how DDD fits into today's development platforms (Java, .NET, etc), and what's been new in the DDD world since 2003.
At the recent Spring Experience conference, InfoQ did a video interview with Eric which will appear on InfoQ in the coming months. One of the questions answered was what are the minimal practices required for one to say they are doing DDD? Eric responded that the two main ones are using the ubiquitous language, and also the bounded context pattern.
