hi, there,
This is a real great book. I like it very much.
Recently, I am studing the Pojo in action as well as Hibernate in action. I notice that the common and different points in the design about the layered architecutre.
In Hibernate in action , the Chapter 8 gives a sample that uses DAO in the facade but in the POJO in action, a repository is used instead of DAO pattern.
In my understanding, two books manage to use the DDD to keep the application layer thiner , that is, push most of the biz logic into the domain model . However
, the POJO in action goes further by introducing the repositroy and put all the database , espeically the collection operations, into it and eventually the service layer ( facace?) is really thin.
My question is , if it is right about my understanding and if right, we can use the DAO pattern in the repository , right? Will it suffer from the over-refactoring problem?
Thanks in advance
OrNot
|