As long as the “artifact” that is supposed to mimic the scenario/process in the business is not hidden in the model the actual implementation can be what ever new cool implementation technique Microsoft or X comes up with. The important thing is that developers that are taking the step from being database-oriented must not build there applications as CRUD’s, because then they have shifted the data-centric thinking from the database to the code. Yes, it’s hard, and it’s even harder with teams where everyone are peers; there’s to little use of mentors in our line of business.

//Daniel

In a new fangled LINQ/Lambda way in C#, maybe this is Func. In the end you still get an object that you can pass around.

Try as we might, I think many of us still think in terms of databases, as the entry level for building stored procedures, tables, etc. is not as high. That’s not say that DDD is not possbile, but I think there are a lot of barriers for wide spread adoption.

Really enjoyed your post.