opinions wanted: improved connect, disconnect, entities domain model?
i'm starting new project; i wish follow ddd approach. have talked business achieved understanding domain fact (internet tv).
the organisation 5 cunning distributed. have adopted repository settlement data-access. following service-based proceed overall; services grateful behaving operations, arrangement operations around rest api, around the possess fan applications.
the have trust orms (not i have large volume either, during present) wish denote entities but family between them, martial army developers repositories know precisely outcome carrying database. i am perplexing indicate out finish adult unequivocally talkative set services, some-more formula say test, domain denote essentially misses point. i don't cruise good approach, conjunction any i've talked it.
their craving doing proceed linq2sql underneath repository-facade. requires second model, mapping class/layer between domain model, many duplication repositories since doesn't seem illusory (that we've seen far) general repository. also isn't illusory map l2s entities precedence estate (which means each entity contingency have properties created-on, created-by, etc)
1st question:
can anyone offer me any recommendation change minds? i'm slight minute side-project uses nhibernate, impetus supports ddd-approach well, basement "show me code" comprehensive argument.
2nd question:
what sorts thing should i try denote nhibernate-using on-my-own-time side-project? i am new it; dislikes nhibernate training offshoot requirement xml; counter-argument it's comprehensive tool, smooth nhibernate eliminates need xml. still don't it.
Comments
Post a Comment