3 ms·

I'd have a scan of Oren Eini's multi-part review of this app before getting too excited about that "enterprisey" app. Here's parts 1 and 2: http://ayende.com/

I'd have a scan of Oren Eini's multi-part review of this app before getting too excited about that "enterprisey" app. Here's parts 1 and 2: http://ayende.com/blog/19457/review-microsoft-n-layer-app-sample-part-i http://ayende.com/blog/19457/review-microsoft-n-layer-app-sa... http://ayende.com/blog/27649/review-microsoft-n-layer-app-sample-part-ii-getting-lost-in-the-architecture http://ayende.com/blog/27649/review-microsoft-n-layer-app-sa... The remainder of the reviews are in July 2011's blog posts. I think the conclusion is that's over-engineered junk.

NicoJuicy 13y ago
I already read that and the author is wrong about the "big picture". I quote: "If it is a simple business scenario, it doesn’t need DDD." The application doesn't explain how to build a contacts manager or something. It explains how to do the DDD-design in .Net, so yes, it's over-engineered for it's current application, that's the whole point. You can learn about the architecture here : http://download.microsoft.com/download/9/F/A/9FA4753A-FC8A-40DE-9EFA-CCAFB4C835FC/DDDNLayeredNET40ArchitectureGuideMicrosoft160513.zip http://download.microsoft.com/download/9/F/A/9FA4753A-FC8A-4... please read that first before breaking it down ;-)