1. Hibernate is fully automatic, while mybatis is semi-automatic
Hibernate can fully operate on the database through the object relational model, and has a complete mapping structure between JavaBean objects and the database to automatically generate sql. While Mybatis only has basic field mapping, object data and actual object relationships still need to be implemented and managed through handwritten sql.
2. The portability of hibernate database is far greater than that of mybatis
Through its powerful mapping structure and hql language, hibernate has greatly reduced the number of objects and databases (oracle Mysql, etc.), while mysql requires handwritten sql, so its coupling with the database directly depends on the programmer's method of writing sql. If SQL is not universal and uses many SQL statements with certain database characteristics, its portability will be greatly reduced and the cost will be very high.
3. Hibernate has a complete log system, while Mybatis lacks some
The hibernate log system is very sound and covers a wide range of issues, including: sql records, relationship exceptions, optimization warnings, cache prompts, dirty data warnings, etc; In addition to the basic recording function, mybatis has many weak functions.
4. Mybatis needs to pay more attention to details than hibernate
Hibernate configuration is much more complex than mybatis, and the learning cost is also higher than mybatis. However, because mybatis is easy to use, it is more concerned about technical details than hibernate. Because mybatis does not need to consider many details, and its development mode is little different from traditional jdbc, it is easy to start and develop projects, but ignoring details will lead to more bugs in the early stage of the project, so it is slow to develop relatively stable software, but fast to develop software. Hibernate is the opposite. However, if you are proficient in using hibernate, the development efficiency is no worse than or even better than mybatis.
5. In terms of SQL direct optimization, mybatis is much more convenient than hibernate
Since MySQL's SQL is written in XML, it is much easier to optimize SQL than hibernate. However, many of hibernate's SQL statements are generated automatically and cannot be maintained directly; Although there is hql, its function is not as powerful as sql. When you see abnormal requirements such as reports, hql also stops eating, that is to say, hql is limited; Hibernate also supports native sql, but its development mode is different from orm, which requires a change of thinking, so it is not very convenient to use. In short, hibernate is not as flexible as mybatis in writing sql.
With the increasing use, I made a further summary:
Mybatis: small, convenient, efficient, simple, direct, semi-automatic
Hibernate: powerful, convenient, efficient, complex, roundabout, fully automatic
mybatis：
1. It is easy to get started, and it is easy to learn and use. It provides the automatic object binding function of database query, and continues the good experience of using SQL. It is perfect for projects without such high object model requirements.
2. More detailed SQL optimization can be carried out to reduce query fields.
3. The disadvantage is that the framework is still relatively simple, and the function is still missing. Although the data binding code is simplified, the entire underlying database query actually needs to be written by oneself, and the workload is also relatively large, and it is not easy to adapt to rapid database modification.
4. The L2 cache mechanism is poor.
hibernate：
1. Powerful functions, good database independence, and strong O/R mapping capabilities. If you are quite proficient in Hibernate and have properly encapsulated Hibernate, the entire persistence layer code of your project will be quite simple, with little code to write, fast development speed, and great pleasure.
2. There is a better two-level caching mechanism, which can use third-party caching.
3. The disadvantage is that the learning threshold is not low, and the proficiency threshold is higher. Moreover, how to design O/R mapping, how to balance performance and object model, and how to make good use of Hibernate require your strong experience and ability.
Take a vivid metaphor:
Mybatis: Mechanical tools are easy to use and can be used as soon as they are taken. However, I still have to do my own work. However, the tools are alive and I decide how to use them.
Hibernate: intelligent robot, but the cost of developing it (learning, proficiency) is very high, and the work can get rid of it, but only limited to what it can do.
