Best Practices - Hibernate save code inside Entity itself?

Question

In the Google RequestFactory they recommend putting my save logic (in my case, Hibernate) inside Entity classes. Then they ask the question: "What if you do not want to embed the save code in the entity itself?" and proceed to explain the alternative method.

My question is: which is better by putting the save logic inside the Entity class or keeping the whole save logic in a separate class?

Any information appreciated, thanks.

-tjw

Answer 1

Bringing the persistence code in the essence itself is an Active Record Pattern approach, while preserving the entire logic of saving in a separate class by the Model Exemplary approach. You can use the repository pattern vs activerecord to find more information about your issues.

For example, an active record template criticizes its testability without a database; you can refer to this for more information.

For me, I prefer the repository template more, because it can be tested and I don’t like save codes, and domian business logic is mixed in one class, which violates the emphasis on separation of problems.