Domain-Driven Design Community

Something like Domain Driven Design from Eric Evans or Patterns of Enterprise Application Architecture (P of EAA) by Martin Fowler or Design Patterns by the

Hi does anyone know if there exist a collection somewhere full of different patterns on how to create different Models? If would be nice if there were... /Mark

If you need return message, why not use CQRS. Greg presentation very nicely. Okey if you have hand coded SQL here is nice example written by Mark Nijhof :

Or you can use some dynamic proxy for that.. Minus of the "update all columns" is that it will cause much higher fragmentation of the database, higher traffic,

I was thinking of a proxy that implements the interface of each entity in the aggregate. It tracks changes as it receives invocations and then reflects the

Thanks Vaughn. Sorry for my ignorance, but the proxy you are talking about here, is that an implementation of the Observer Pattern? So, once properties of an

Greg, btw what about you? Are you using pure interfaces to define your models? I remember these two posts that I read some year ago:

... We are using Qi4j in Java, where all domain models are defined with interfaces+mixins, so yes. The main gain for us is that we can have domain objects with

Hey folks, First of all, I apologize if the formatting doesn't work out. I pretty much copied this straight from my post at stackoverflow.com.

We are not currently using interface based programming. One of the reasons is that we many classes with lot of properties. Adding interface for everything

I can't remember all the details now but they were all related to the Open/Closed Principle. A case was simply related to a sealed EventArgs defined in a

- EventHandler making some interfaces depends upon concrete classes (in rare cases it has been an issue) Can you give an example? ... -- Les erreurs de

Please: if you would reply "NO! CERTAINLY NOT": I'd like to know your opinion about the reason of your choice. Giacomo

Are you using interface based programming while developing your domain models? On our biggest projects we took such approach and we have found it good. It

I know there is a large subset that reads this blog and/or follows me on twitter and/or is on the ddd list but for those who are not in those sets.

In hope of bringing the DDD list back to a focus of DDD I created a second list for Event Sourcing/CQRS/etc type discussions as I am sure many of the people on the DDD list feel spammed with the ideas. The list already has some great discussions on it and I think will become a great resource for those looking to learn the ideas.

 

 

To me these statements contradict. If a repository or whatever is backing the repository is "smart" enough to figure out what changed, then why do you need any

I replied earlier but was never posted. If you are looking for some way to diff your aggregate instances you are going to need some kind of UoW. I am not

I'm totally against the idea of this database design, but it has been there for over 10 years and I joined this company less than 2 years ago. It's not

... Relationships, etc. Isn't this what a database does anyways? Might be a good time to ask what you are gaining by rebuilding the functionality of a

I mean't that 'smart' repository would new which properties of object have changed and would persist only these. This is not a direct responsibility of a