During my "Next-Generation Data Access with ADO.NET Orcas" talk yesterday at the December Software Developer Event the question came up how to start with this DDD thing. With the ADO.NET Entity Framework on the horizon developers seem to be anxious to learn more. Which is of course a great thing! I couldn't hold myself from evangelizing DDD and offered to post a couple of links on this blog to get you guys started.
For a quick introduction see Domain-Driven Design Quickly, InfoQ.com (you'll have to register).
Two excellent books:
Domain-Driven Design Tackling Compexity in the Heart of Software, Eric Evans
Applying Domain-Driven Design and Patterns in C# and .NET, Jimmy Nilsson
Also see part 1, 2, 3, 4, 5 and 6 of this series of posts on the next-generation data access for the .NET platform. Please note that this information is subject to change.
There will an edm.exe tool in the SDK to generate source code from your csdl file (discussion).
There will be stored procedure support for two scenarios: 1) Override change processing for a given EntitySet/Entity type, it will bypass the internal change processing infrastructure and instead bind the properties of the entity to store procedure parameters and then execute the stored procedure. 2) Retrieve data by doing selects directly against the logical schema (discussion).
Relaxing the requirement for entities to derive from Entity base, and should implement IEntity instead (discussion).
Map multiple schemas to a single EDM schema (discussion).
Support for computed colums (discussion).
No support for mapping across different database connections. I is however possible to have multiple entity containers within a single server instance (discussion).
Most likely there will be support for Oracle (discussion) in V1.