Entity Interface - an antipattern?

Question

Java

Greetings!
Life forces us to separate the DAO level into a separate artifact, for ease of migration to another data store.
I found that models (entity) often have a lot of hung annotations that are not applicable in the new repository and its ORM.
Since entities are used at the service level, which remains generic, accordingly, there is an idea to separate interfaces from the entity and use them at the service level.
Is this a normal implementation or is it still not in line with the idea of ​​beauty?

Answer 1

For full portability between different data sources, it is necessary that the dao methods return DTOs, and not stored entities. It is desirable to make DTO-shki immutable and put it in dao-api. In the implementation of dao, you will also need to make a mapper between entities and dto-shki.

Answer 2

Life forces us to separate the DAO level into a separate artifact

Well, pick it out. Then, when you migrate completely, you still have to do a little refactoring. Fix that as well. And there you look and the situation will be different.

Answer 3

I didn’t quite understand the question, do you want to abandon the DAO?
If so, then for example, they did it in spring roo, all DAO methods are static and belong to the entity class.