Is there a reason to separate `Model` and `Entity` classes?

Question

In a recent interview with Amazon I have been rejected because I could not tell the advantage and disadvantage of making model and Entity classes different and same.

I have always created Model and Entity class same.

Can anybody help me on that with an example? Interviewer said you are making strong binding of UI+DB if you are keeping it same.

this might answer your question https://www.quora.com/What-is-the-difference-between-a-model-object-and-a-entity-in-Spring-Boot — Harmandeep Singh Kalsi, May 24 '20 at 15:05

score 2 · Answer 1 · answered May 24 '20 at 15:05

It's true by making same class for Entity and Model you are tightly binding UI and DB, simple example of why should avoid is -> most of the time, we modify response like adding DTO, modifying format of date and so on. which could impact your database calls (DTO layer).you can read more here

Is there a reason to separate `Model` and `Entity` classes?

1 Answers1