.net - Is Repository pattern an overkill -
I have been using repository patterns (DDD and POEA) for a while. Although some members of our team have argued that this is just an additional layer of intangible and unnecessary. I can see some benefits in their arguments. The modern ORM solution (NHibernate or EF) has almost everything I need to find and find some articles on this article. So what's the repository pattern overkill?
This depends on the complexity of your problem and the domain model plays a simpler solution in your role resolution , Possibly the repository overkill but for complex domains with a strong language and developed requirements / requirements, the repository is a good, clean abstract that owns the domain object life cycle. Many ORMs will do a lot of these, but, in a complex domain, there is always some domain activity that is understood in a repository and which is not supported outside of the box by any ORM.
Bottom line: It depends on context.
Comments
Post a Comment