是Asp.Net MVC + CSLA + DDD可能 [英] Is Asp.Net MVC + CSLA + DDD Possible

问题描述

我被要求审查一个系统，该系统是基于ASP.NET MVC + CSLA + DDD（领域驱动设计）的一天。该系统的第一个版本是基于ASP.NET MVC + CSLA。第二个版本是基于加上新增的DDD。究其原因是因为.....好了，我不知道是什么。当我看着从两种不同的架构图中，它是pretty明显，第二个版本是非常复杂的多。里昂证券主要对象所使用的域对象。当你看到这样的事情你知道它已经闻起来却是很难用了很长的时间来证明为什么有人不应该这样做没有一个这样），其所有主题或B极端的知识）。我既没有这些对于这个话题，但我知道如果我建立了这个从无到有我不会做这种方式，也不会没有很多的开发者与我联系在一起。

所以，亲爱的读者，你会在这种情况下怎么办？我的想法是，如果你想使用CSLA和MVC和DDD，那么你做一个立场，选择一种或另一种（或CSLA DDD）。如果不这样做也有在厨房里厨师太多。

请流下了一些见解，如果你对此事的看法。

解决方案

  

我的想法是，如果你想
  使用CSLA和MVC和DDD，那么你做
  一站，并选择一种或另一种（CSLA
  或DDD）。如果不存在太多
  许多厨师在厨房里。

我倾向于有同意你的看法。如果有人想这样做DDD与已经冲出DDD友好的架构+支撑框架，我建议你小号＃命令arp架构在CSLA。

话虽这么说，有些人觉得这是可能采取的一些DDD的使用CSLA方面。显然，一个纯粹DDD可能会畏缩在这样的前景，但你并不一定要获得从DDD东西纯粹。德里克·贝利有关于主题的有趣的博客：的http：/ /www.avocadosoftware.com/csblogs/dredge/archive/2007/02/19/687.aspx

I was asked to review a system the other day that 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 that plus added DDD. The reason is because..... well, I don't know what. As I looked at the diagrams from the two different architectures, it was pretty apparent that the second version was extremely more complex. The CSLA objects basically used the Domain objects. When you see something like this you know it already smells but it is hard to justify why someone shouldn't do it this way without A) having extreme knowledge of all topics or B) using it for a long time. I have neither of these for this topic but I know if I'd built this from scratch I wouldn't have done it this way, nor wouldn't a lot of developers I associate with.

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 make a stand and chose one or another (CSLA or DDD). If you don't there are too many cooks in the kitchen.

Please shed some insight if you have opinions on this matter.

解决方案

My thoughts are that if you want to use CSLA and MVC and DDD then you make a stand and chose one or another (CSLA or DDD). If you don't there are too many cooks in the kitchen.

I tend to agree with you there. If someone wants to do DDD with an already flushed out DDD friendly architecture + supporting frameworks, I'd recommend S#arp Architecture over CSLA.

That being said, some people feel it is possible to take on some of the aspects of DDD using CSLA. Obviously a DDD purist would probably cringe at that prospect, but you don't have to be a purist to gain something from DDD. Derick Bailey has an interesting blog regarding the topic: http://www.avocadosoftware.com/csblogs/dredge/archive/2007/02/19/687.aspx

这篇关于是Asp.Net MVC + CSLA + DDD可能的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！