That was just a simple usage example, probably not the best from a functional perspective. But is it a good idea to introduce a new business service just to
Given the right tools you can leverage DDD or at least domain modeling best practices for any project. If you were developing software with Smalltalk in the
... Yup. The repository interface is part of the domain model. The implementation, of course, is what does the actual marshalling to the persistence store,
Wouldn't you have: class Car { Engine installedEngine; public installEngine(Engine engine) { this.installedEngine = engine; } } And a Service Layer would call:
Hi Dan, are you certain? Fowler defines Repository as follows: "Mediates between the domain and data mapping layers using a collection-like interface for
Hi Çevik, ... Well, they refer to each other conceptually but they don't share the same time line. For instance you may register an Engine before registering
... The interface definition (ICustomerRepository, say) is part of the domain, but the implementation (CustomerRepositoryNHibernate) is part of infrastructure.
Otherwise, how would you lookup another aggregate root from one aggregate root in the following scenarios: 1. As association (instance variable in class) -
Hi Ali, as far as I understand, the Repository is NOT inside the Domain Layer as you state. You would retrieve an Aggregate Root via its Repository, and then
sometimes, you just gotta use the right tool for the right job...unless you see you see this little app scaling a lot more than it is (in turns of features
PETE! Haven't seen you on the list for a while. Recently read: Xml is like violence. If it isn't working you aren't using enough of it :) But seriously.
Not sure what you want people to say. What would your events be if you don't have commands? Aside from that you could do it in the same way the simple sample
Hi all My client app talks to a DB app. It sends it either a query or a command and gets a response, for example var query = new Order_ViewQuery(...id of