This chapter presents an overview of the Domain-Driven Design (DDD) concept and explains its capabilities and features. Here is a brief outline of the topics covered in this chapter:
Domain-Driven Design
The Domain layer of the sample application
The Infrastructure layer of the sample application
DDD is not a technology or methodology. It is a way of thinking and a set of priorities aimed at accelerating software projects that have to deal with complicated domains (http://www.domaindrivendesign.org ).
For many years, designing and realizing JEE application has meant moving Data Transfer Objects (DTO) and Value Objects (VO) between layers and writing procedural code to allow Enterprise JavaBeans (EJB) to do their work.
This led to the use of classes that were defined as anemic by Martin Fowler (http://martinfowler.com/bliki/AnemicDomainModel.html), that's to say, classes where the business logic is completely...