Domain-Driven Design, or DDD, is an envelope that encapsulates software design theory and technique as well as theory and technique for communication. The focus of the DDD brand is to increase developers’ capability to manage complexity in software design.

Some of the targeted complexity is tactical in nature (technical code bits) and some of the targeted complexity is strategic in nature (planning, communication).

A community of developers (and others) has formed around DDD. Therefore, it’s to be understood that this community is made up of individuals who join a social context in order to network and collaborate with people and ideas related to managing complexity in software design.

The DDD community is diverse and accepting. On average, DDD communicators are experienced developers, often with team leadership experience. The community is widely respected due to shared interest in understanding engineering trade-offs and seeking to discover consistently more effective models.

Below begins the original article.

A Brief Introduction

Domain-Driven Design (or DDD) is a software development approach that focuses on the domain model first. Techniques within DDD allow teams to separate various “domains" (related parts of the application) from one another with the resulting benefit of trading away generic models that hold the behavior for many contexts with models designed to a specific context.

DDD is linguistic, analytic, and strategic. It encompasses many areas of software design including interacting with clients and implementing design-patterns.

Tactical Patterns

At Laracon NYC, I gave a talk on command oriented interfaces and domain-events. These patterns are often utilized with DDD but are themselves not a core concept of DDD at all.

A UseCase Architecture by Shawn McCool

As I mentioned during the talk, the talk was not about DDD. But rather, was inspired by the rich service layer movement that seems to be flowing from DDD through our community.

I have begun to create a video series to go over many tactical components of domain-driven design at The series focuses on programming techniques including CQRS and Event Sourcing.

Models and Service Layers - Hemoglobin and Hobgoblins by Ross Tuck

I believe that many developers (like me) started to get a taste of the benefits that DDD has to offer and decided that they wanted more.

But, what is DDD exactly?

Introduction to DDD

At first, DDD seems like a nebulous concept full of other nebulous concepts. However, during my pursuits I’ve started to nail down specific resources that I believe can give clarity to these ideas.

Vaughn Vernon (the author of the red book –more info later–) gave two presentations at TechEd North America 2014 that are startlingly good introductions to DDD. The first covers the core concepts of DDD including the ubiquitous language, domains, bounded contexts, context mapping, and aggregation.

How You Can Architect and Develop Enterprise Mission-Critical Applications with Domain-Driven Design

Vaughn’s second session covers implementing aggregates and entities effectively. He utilizes .NET however the concepts hold true, so PHP developers don’t be scared away.

How You Can Implement Aggregates and Domain Entities Effectively in Domain Models, with .NET

So far, these are the best introductions to DDD that I have found. Once you have consumed these videos, you may have a desire to dig further. If you’re like me, you’re very interested in these strategies for understanding and developing enterprise applications.

Read the Source Material

When you’re ready, it’s probably time to grab the blue and red books.

The book Domain-Driven Design by Eric Evans is considered to be the seminal work. It’s heavy on concepts and light on implementation. We’re software engineers. We focus on code and design-patterns on a regular basis. It is my belief that while we study more design-patterns, techniques, and tools, we have not been growing as steadily in terms of strategic domain modeling. There is more than one side to the development coin and DDD is helping me to see how I can grow in ways separate from the object-oriented paradigm.

Implementing Domain-Driven Design by Vaughn Vernon (yes, the speaker mentioned earlier in this post) is an evolution of Eric Evan’s book in that it provides additional explanations and ideas. However, it focuses much more heavily on implementation than the blue book. Implementing Domain-Driven Design discusses ideas about handling access control, implementing context maps, and many other code-focused topics. It is my personal opinion that this book is best digested after reading Evans’ blue book.

Between these works, we have enough to begin mastering DDD.

Online Reading Resources

Aside from the books, we have a number of online resources to assist us. This list will be updated as I find more material.

Video Resources

And last but not least… The PHP Friends of DDD have compiled a massive “State of the Union" index of resources.