Skip to Content
Domain-Driven Design: Tackling Complexity in the Heart of Software
book

Domain-Driven Design: Tackling Complexity in the Heart of Software

by Eric Evans
August 2003
Beginner to intermediate
560 pages
12h 58m
English
Addison-Wesley Professional
Content preview from Domain-Driven Design: Tackling Complexity in the Heart of Software

Footnotes

Chapter 1

1. Brian Marick mentioned this example to me.

Chapter 5

1. A model ENTITY is not the same thing as a Java “entity bean.” Entity beans were meant as a framework for implementing ENTITIES, more or less, but it hasn’t worked out that way. Most ENTITIES are implemented as ordinary objects. Regardless of how they are implemented, ENTITIES are a fundamental distinction in a domain model.

2. The WHOLE VALUE pattern, by Ward Cunningham.

Chapter 6

1. David Siegel devised and used this system on projects in the 1990s but has not published it.

Part III

1. Patterns as targets for refactoring were briefly mentioned in Gamma et al. (1995). Joshua Kerievsky has developed refactoring to patterns into a more mature and useful form (Kerievsky ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Designing Data-Intensive Applications

Designing Data-Intensive Applications

Martin Kleppmann

Publisher Resources

ISBN: 0321125215Purchase book