Home/ Questions/Q 7564201
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T13:51:14+00:00

I am reading Eric Evans book about DDD and I have a question to

  • 0

I am reading Eric Evans book about DDD and I have a question to the following quote. How do you make your equals() method when you should not use the attributes? I am using JPA and I have a id attribute which is unique but this is not set until you actually persist the entity. So what do you do? I have implemented the equals method based on the attributes and I understand why you shouldn’t because it failed in my project.

Section about entities:

When an object is distinguished by its identity, rather than its
attributes, make this primary to its definition in the model. Keep the
class definition simple and focused on life cycle continuity and
identity. Define a means of distinguishing each object regardless of
its form or history. Be alert to requirements that call for matching
objects by attributes. Define an operation that is guaranteed to
produce a unique result for each object, possibly by attaching a
symbol that is guaranteed unique. This means of identification may
come from the outside, or it may be an arbitrary identifier created by
and for the system, but it must correspond to the identity
distinctions in the model. The model must define what it means to be
the same thing.

http://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Couple approaches possible:

    • Use a business key. This is the most ‘DDD compliant’ approach. Look closely at domain and business requirements. How does your business identify Customers for example? Do they use Social Security Number or phone number? How would your business solve this problem if it was paper-based (no computers)? If there is no natural business key, create surrogate. Choose the business key that is final and use it in equals(). There is a section in DDD book dedicated to this specific problem.

    • For the cases when there is no natural business key you can generate UUID. This would also have an advantage in distributed system in which case you don’t need to rely on centralized (and potentially unavailable) resource like database to generate a new id.

    • There is also an option to just rely on default equals() for entity classes. It would compare two memory locations and it is enough in most cases because Unit Of Work (Hibernate Session) holds on to all the entities (this ORM pattern is called Identity Map). This is not reliable because it will break if you use entities that are not limited to the scope of one Hibernate Session (think threads, detached entities etc)

    Interestingly enough, ‘official’ DDD sample uses a very lightweight framework where every entity class is derived from Entity interface with one method:

    boolean sameIdentityAs(T other) 
// Entities compare by identity, not by attributes.
    • 0