I am currently in the process of designing a system which will use multiple data sources to consume the required data. I am attempting to model the concepts shown below (would post an image but don\'t
What are any reccomendations for the following. I have a structure like this. --ApplicationServices --Domain
None of the examples I have looked at for Repository Patterns include any kind of error handling. Why is this? Say for instance I have this:
I need to clarify something. Have Person Aggreagate , 2 VOs (Country, StateProvince). I want to load all country in my presentation layer (i am using mvc)
It is recommended to have one repository per aggregate. However, I have a case where the same aggregate object can be fetched from 2 heterogeneous data stores. For the background, that object is:
I am trying to come up with a generic way to pull an object by its Id in my repository. In my database, generally, all the IDs are primary keys and are of the type integer. There may be a case, down t
Based on the following definitions from Domain-Driven Design: Tackling Complexity in the Heart of Software,
I\'ve just started a new project and have naturally opted to use a lot of new tech. I\'m using (Fluent) NHibernate, ASP.NET MVC 3 and am trying to apply the Repository pattern.
I am using NUnit for test units. I have my interface on the domain so i am ready to make implementation of those interfaces in the persistence layer. My question is how do you actually make the unit t
I have a system that talks with the database using repositories. What is the correct definition when it is a remote service? Or better,
加载中,请稍侯......