Domain-Driven Design Community


Four Strategies for Dealing with Legacy Systems When an elegant new design concept gets injected into an entrenched legacy system, it typically gets compromised to death because the legacy is an immovable object. This tempts teams into ambitious legacy replacement projects that often run aground, or disappoint. In this talk for the New York DDD meetup in August 2011, Eric Evans describes four strategies for doing DDD in an environment dominated by messy legacy systems while delivering business value quickly, taking into account different levels of capability and commitment to DDD in the organization.
RESTful SOA or Domain-Driven Design Vaughn Vernon advocates using DDD’s Context Mapping when integrating services in a RESTful SOA implementation, avoiding one of SOA’s pitfalls: focusing on services rather than the domain. (QCon SF November 2010)
Greg Young at NDC2010 "7 Reasons DDD Projects #FAIL" Many people try applying Domain Driven Design and fail miserably. This presentation looks at seven top reasons for failure and discusses how to avoid them.
Escaping Legacy while Avoiding Strategic Traps Eric Evans discusses the need for strategic thinking and how early design decisions have major impact on the organization and the entire development process. Strategic Design can move you quickly to dramatic business value and reduce the risk of project failures.
Eric Evans: What I've learned about DDD since the book In this talk, first presented at QCon London 2009, Eric Evans describes what he'd learned about DDD since the book was published. The talk was recorded at the May meeting of DDD-NYC SIG.

Four Strategies for Dealing with Legacy Systems

When an elegant new design concept gets injected into an entrenched legacy system, it typically gets compromised to death because the legacy is an immovable object. This tempts teams into ambitious legacy replacement projects that often run aground, or disappoint. In this talk for the New York DDD meetup in August 2011, Eric Evans describes four strategies for doing DDD in an environment dominated by messy legacy systems while delivering business value quickly, taking into account different levels of capability and commitment to DDD in the organization.

RESTful SOA or Domain-Driven Design

Vaughn Vernon advocates using DDD’s Context Mapping when integrating services in a RESTful SOA implementation, avoiding one of SOA’s pitfalls: focusing on services rather than the domain. (QCon SF November 2010)

Greg Young at NDC2010 "7 Reasons DDD Projects #FAIL"

Many people try applying Domain Driven Design and fail miserably. This presentation looks at seven top reasons for failure and discusses how to avoid them.

Escaping Legacy while Avoiding Strategic Traps

Eric Evans discusses the need for strategic thinking and how early design decisions have major impact on the organization and the entire development process. Strategic Design can move you quickly to dramatic business value and reduce the risk of project failures.

Eric Evans: What I've learned about DDD since the book

In this talk, first presented at QCon London 2009, Eric Evans describes what he'd learned about DDD since the book was published. The talk was recorded at the May meeting of DDD-NYC SIG.

Strategic Design in Evans' Book

Strategic Design is addressed in depth in the book Domain-Driven Design, by Eric Evans, Part IV:

Chapter 14, Maintaining Model Integrity, explains Bounded Contexts and their relationships and the use of Context Maps

Chapter 15, Distillation, explains Core Domain and how to focus development by distinguishing the differentiating areas of the domain from the generic ones.

Chapter 16, Large-scale Structure, explains how we can sometimes apply broad patterns to a system through Evolving Order.