Hibernate is still a lightweight packaging on a more basic CRUD operation. I feel that I should also be packaged in the Hibernate (or still reserved) into DAO, because the direct CRUD operation does not meet the business logic used by the business layer or the performance layer. Object. You can understand the location of Hibernate, according to the original approach, when you write DAO yourself, Hibernate replaces the code that is originally written to SQL. Of course, Hibernate's ability is more than that, it also has the advantages of easy to use connecting pools. But Hibernate's essence is easy to make CRUD operations in the way.
For introduction of Hibernate, most of them are not suitable for Framework using third parties, because the general third-party Framework has implemented their own DAO layers. It actually uses to use a persistence layer when building a new application.