Mainly through the three perspectives of flexibility , performance, and development speed
1. ibatis is very simple and easy to learn, while hibernate is relatively complex and has a high threshold.
2. Both are relatively excellent open source products
3 . When the system belongs to secondary development and cannot control and modify the database structure, the flexibility of ibatis will be more suitable than hibernate4
. The system has a huge amount of data processing and extremely demanding performance requirements, which often means that we must use highly optimized SQL statements (or stored procedures) to achieve system performance design indicators. In this case ibatis will have better controllability and performance.
5. Ibatis requires handwritten sql statements , and can also generate some of them, while hibernate can basically generate them automatically, and occasionally write some hql. For the same requirements, the workload of ibatis is much larger than that of hibernate . Similarly, if it involves the modification of database fields, hibernate modifies very few places, and ibatis needs to modify those sql mapping places one by one.
6. The po obtained by the one-to-one mapping of database fields and the po obtained by the object mapping of hibernte are completely different. The essential difference is that this po is flat, unlike the po mapped by hibernate, which can express stereo object inheritance. Aggregation and so on, which will directly affect the design of your entire software system.
7. Hibernate is now the mainstream o/r mapping framework. From the richness of documents, the completeness of products , and the speed of version development, it is stronger than ibatis.