Domain Driven Design Quotes

The heart of software is its ability to solve domain-related problems for its user.

It takes fastidiousness to write code that doesn’t just do the right thing but also says the right thing.

A model is a selectively simplified and consciously structured form of knowledge.

When you can, choose Value Objects to model integrations. This advice is applicable in many cases when consuming remote Standard Types.

It is more desirable for Entities to have equals() and hashCode() methods that are based on the object’s unique identity rather than other attributes.

The vital detail about the design is captured in the code. A well-written implementation should be transparent, revealing the model underlying it.

Listen to the language the domain experts use. Are there terms that succinctly state something complicated? Are they correcting your word choice (perhaps diplomatically)? Do the puzzled looks on their faces go away when you use a particular phrase? These are hints of a concept that might benefit the model.

Developing software that delivers true business value is not the same thing as developing ordinary business software. Software that delivers true business value aligns with the business strategic initiatives and bears solutions with clearly identifiable competitive advantage—software that is not about technology, but about the business.

One of the patterns from domain-driven design is called bounded context. Bounded contexts are used to set the logical boundaries of a domain’s solution space for better managing complexity. It’s important that teams understand which aspects, including data, they can change on their own and which are shared dependencies for which they need to coordinate with other teams to avoid breaking things. Setting boundaries helps teams and developers manage the dependencies more efficiently. The logical boundaries are typically explicit and enforced on areas with clear and higher cohesion. These domain dependencies can sit on different levels, such as specific parts of the application, processes, associated database designs, etc. The bounded context, we can conclude, is polymorphic and can be applied to many different viewpoints. Polymorphic means that the bounded context size and shape can vary based on viewpoint and surroundings. This also means you need to be explicit when using a bounded context; otherwise it remains pretty vague.

outside the boundaries of its own skin—these things had driven the species to the edge of destruction. Worse, this one organism threatened the survival of all life on Earth. The Silencer’s makers did not have to look far for a solution. The answer lay in another species that had conquered the entirety of its domain, ruling it with unquestioned authority for millions of years. Beyond their immaculate design, the reason sharks rule the ocean is their complete indifference to everything except feeding, procreation, and defending their territory. The shark does not love. It feels no empathy. It trusts nothing. It lives in perfect harmony with its environment because it has no aspirations or desires. And no pity. A shark feels no sorrow, no remorse, hopes for nothing, dreams of nothing, has no illusions about itself or anything beyond itself. Once a human named Evan Walker had a dream—a dream it can no longer remember—and in that dream there was a tent in the woods and in that tent there was a girl who called herself humanity, and the girl was worth more to it than its own life. No longer. When it finds her,