👨‍💻
Software Engineering
Implementing Domain Driven Design
Implementing Domain Driven Design
  • Intro
  • 1. Getting Started with DDD
    • The Business Value of DDD
  • 4: Architecture
  • 5: Entities
    • Why We Use Entities
    • Unique Identity
  • 6: Value Objects
    • Value Object Characteristics
    • Integrate with Minimalism
    • Standard Types Expressed as Values
    • Resources
  • 10: Aggregates
  • 8: Domain Events
    • The When & Why of Domain Events
    • Modeling Events
    • Publishing Events from the Domain Model
  • 13: Factories
  • Resources
Powered by GitBook
On this page

5: Entities

Caution: Avoid "Entity-Think"...

  • There is a tendency for developers to focus on data rather than the Domain.

  • This is often due to prevailing approaches to software development that place importance on the database.

  • Instead of designing domain concepts with rich behavior, we think about attributes (columns) and associations (foreign keys) of the data.

  • This often leads to every concept in the Domain Model being coded as an Entity with getter & setter methods.

  • This is NOT the only behavior DDD entities should have.

Previous4: ArchitectureNextWhy We Use Entities

Last updated 1 year ago