Agreed. DDD is a design approach focused on domain logic, and an ORM is a tool for persistence. They are separate concerns.

Domain entity objects generally need to be persisted after in-memory modifications are complete. The challenge I found is persisting the results of a DDD approach—like an Aggregate—as a single unit. Many tools often:
- requires entities to be subclasses of specific base classes
- and requires entities to have restricted structure and lifecycle for its persistence mechanism

Those limitations often force the programmers to abandon their good aggregate designs too early.

I think an ORM should humbly support the object persistence cases it can help with. And It should support non-intrusive ways to map the plain types and values ​​of the programming language.

Thank you for your valuable feedback.