Domain-Driven Design is a subject where there currently are very few examples of how to actually do it in practice. In this article, Srini Penchikala gives you guidelines, practices, frameworks and tools that technical leads and architects can use in the effort of implementing a system in a Domain-Driven way.
From the article:
Domain Driven Design and Development is also influenced by several architectural, design, and implementation aspects such as:
- Business Rules
- Persistence
- Caching
- Transaction Management
- Security
- Code Generation
- Test Driven Development
- Refactoring
This article talks about how these different factors affect the implementation project throughout its lifecycle and what the architects should look for in realizing a successful DDD implementation. I will start off with a list of characteristics a typical domain model should have, and when to use a domain model in an enterprise (versus not using a domain model at all or using an anemic domain model).
After that initial effort, Srini guides you though Project Management, Architecture, Design, Development, Unit Testing/Continous Integration and Deployment of a domain driven application. A sample applictaion is provided with the article.
If you want to understand how annotations, dependency injection, code generation, transaction management, data transfer objects and many other things fits into a DDD-context - read the full article on Domain Driven Design and Development In Practice.
