Geek asks and answers

MVC + WCF + TDD or DDD Architecture

Here we are again at the crossroads.

I want to try to implement, at least for the next 3 years, a simple, proven way to archive my applications. Each time I am about to start a project, this is like the first time because of the sheer number of “ways” to create sites these days.

I have this code code that I got from this package, I bought C # Design Pattern Framework 4. Among the several projects that they have, there is one called Design Patterns in Action. You can download it here https://skydrive.live.com/redir?resid=B853B0DB724C30E5!16735&authkey=!AOeHSAWa_P4vzzU

My question is, after you look at this decision, what is good, bad, what would you save, what would you delete, what is superfluous, etc. etc. in this example?

I understand that they are trying to show several clients, as well as several DAOs. But in general, would this architecture be the one you would take as a "template"? Thank.

+5
source share
3 answers

My question is, after you look at this decision, what is good, bad, what would you save, what would you delete, what is unnecessary, etc. etc. about this example?

After a quick look, here is what I would say:

  • DDD , , . - anemic, , DDD- (, ..)

  • - , - - CRUD, .

  • ActionService, , , . , ( , , , ). , (SRP).

  • DAO , .

  • , ?

, , , .

+2

:

  • "" .
  • ""
  • "" .

:

  • - - ?
  • - , ? ?
  • - ?
  • - ?
  • - - ? ?

, , , , , 3 . MVC, WFC, TDD, DDD .. tools, right , .

: , ( , ), .

+4
  • .
  • .
  • /, .

, , . TDD , , .., . - , . , 6 , , , , , :)

0

More articles:


All Articles