I was asked to review the system the other day, which was based on ASP.NET MVC + CSLA + DDD (Domain Drive Design). The first version of this system was based on ASP.NET MVC + CSLA. The second release was based on the addition of DDD plus. The reason is that ... well, I don't know what. Since I was looking at diagrams from two different architectures, it was pretty obvious that the second version was extremely complex. CSLA objects mainly used Domain objects. When you see something like this, you know that it already smells, but it’s hard to justify why someone should not do it this way without A) having extreme knowledge of all topics or B) using it for a long time time. I don’t have any of them for this topic, but I know if I built it from scratch I wouldn’t do it that wayand there wouldn’t be a lot of developers with whom I communicate.
So, dear reader, what would you do in this situation? My thoughts are that if you want to use CSLA and MVC and DDD, then you create a stand and choose one or the other (CSLA or DDD). If you do not, there are too many cooks in the kitchen.
I apologize if you have any opinions on this.
source
share