Hello, and welcome to Domain-Driven Design Fundamentals, part of the ASP.NET MVC 5 Learning Path here at Pluralsight. Your authors, Steve Smith and Julie Lerman, are looking forward to helping you learn the fundamentals of Domain-Driven Design (DDD) through a demonstration of customer interactions and a complex demo application.
Along the way, you’ll learn about elements of a domain model, aggregates in Domain-Driven Design, and repositories. You’ll also get hands on modeling problems, and learn about technical components of DDD, and how to manage complexity.
So if you’re ready to get started, Domain-Driven Design Fundamentals is waiting for you. Thanks again for visiting us here at Pluralsight!
What is Domain Driven Design?
Domain Driven Design (DDD) is a way of more easily developing complex software by strongly connecting all of the software's related pieces into an ever-evolving model of the core business logic.
What exactly is "domain" in DDD?
The domain in domain driven design is the "sphere of knowledge and activity around which the application logic revolves". It's the thing we want the application to apply to.
Some benefits of DDD include that it provides patterns to solve difficult software problems, and even business problems, it creates business logic by putting everything in terms of the business domain, and it mitigates misunderstanding between dev teams and domain experts.
Julie Lerman is a Microsoft MVP, .NET mentor and consultant who lives in the hills of Vermont. You can find Julie presenting on data access and other Microsoft .NET topics at user groups and conferences around the world. Julie is the author of the highly acclaimed "Programming Entity Framework (with a second edition coming soon) and authors the MSDN Magazine Data Points column.