Could not fit this into a tweet in response to a request.
Here are some resources for how EF can be a partner to a Domain Driven Design world:
Update June 2015:
Microsoft Ignite, Chicago May 2015
Domain-Driven Design for the Database Driven Mind (90 minute presentation video on Channel 9)
Update: October 2014:
MSDN Mag Oct 2014 Issue:
Data Points: A Pattern for Sharing Data Across Domain-Driven Design Bounded Contexts
Julie Lerman explores a way to mirror data as one scenario for sharing data across DDD bounded contexts.
MSDN Mag Dec 2014 Issue:
Data Points: A Pattern for Sharing Data Across Domain-Driven Design Bounded Contexts : Part 2 (will provide link when available)
Video: Oredev, Fall 2013 (by me)
ENTITY FRAMEWORK IN CORE-BUSINESS APPLICATIONS THAT LEVERAGE DDD
Video: TechEd North America, May 2014 (Vaughn Vernon)
How You Can Implement Aggregates and Domain Entities Effectively in Domain Models, with .NET
MSDN Magazine Data Points Column (by me) Aug, Sept & Oct 2013
Coding for Domain-Driven Design: Tips for Data-Focused Devs, Part 1
Coding for Domain-Driven Design: Tips for Data-Focused Devs, Part 2
Coding for Domain-Driven Design: Tips for Data-Focused Devs, Part 3
Domain modeling with Entity Framework Scorecard (Jimmy Bogard)
Bonus for NHibernate Converts:
And for those who are looking for this by way of moving from DDD + NH, Jimmy Bogard did a great post (with pointers to related posts) on Migrating from NHibernate to EF.
Sign up for my newsletter so you don't miss my conference & Pluralsight course announcements!
6 thoughts on “Some DDD+EF Resources”
Check out also the DotNetRocks conversation on DDD that Steve Smith & I did recenlty (bit.ly/DNR_DDD) and of course our Pluralsight course, DDD Fundamentals where we do use EF in the solution (bit.ly/PS-DDD)
I’ve read Jimmy bogards “EF scorecard” blog post. ( https://lostechies.com/jimmybogard/2014/04/29/domain-modeling-with-entity-framework-scorecard/ ). He recommends to not use value objects in combination with EF because of null handling issues. Yet in a lot of your DDD related posts and video’s you do display Value Objects in combination with EF.
What is your opinion on this? Do you agree that i should be avoiding VO’s (for example an Address VO)?
(im about to start developing my first DDD + EF application and im trying te avoid common pitfalls.)
Read your blogs on DDD and have learnt a lot.
I have a question regarding aggregate roots.
If aggregate roots are supposed to control access of all other entities in a bounded context then will that not make all other entities of that context anemic ??
I wouldn’t say that aggregate roots should control access of all entities in the context. You might have more than one aggregate root. Also, there are still things that the non-root entities can control. best way to explain is to somewhere that I’ve alrady done it: the DDD Fundamentals course on Pluralsight. Is that an option for you?
I suppose there is an trial period option on pluralsight, will try that. Thanks.
I have learned a lot about DDD by help of your articles.
for the ones who did not read the second part of “Data Points: A Pattern for Sharing Data Across Domain-Driven Design Bounded Contexts” here is the link: