Domain Driven Design for Data Developers

In this course we will learn why you should not use entity models in your user interface and how you would use Domain Driven Design instead. Together we will develop an Entity Framework model, a domain model, a WCF Data Service and an MVC site that will work as an Enterprise Level application. Our Data Layer will be EF over SQL. We will use WCF to pass data to/from our data layer and UI. The UI will only know the domain model and data service. The M of MVC will be our external Domain Model, the V will be Razor view and the C will simply control the view. All the heavy lifting and data transformations will be in our WCF Data Service.

Ken Lovely

Ken is an innovative Information Architect with 20 years’ experience specializing in Microsoft platform technologies. He holds several Microsoft certifications; MCSE, MCPD, MCDBA, MCTS. He has designed and developed systems for financial, banking, cable and insurance industries.  He has strong system development and diagnostic skills. He has been training developers for 10 years. Besides developing data systems Ken also programs lighting software that he uses to light up his neighborhood at Christmas time –