hibernate与ibates优缺（hibernate与ibates优缺）.docVIP

hibernate与ibates优缺（hibernate与ibates优缺） Advantages and disadvantages and feasibility analysis of IBatisNet and Hibernate 1. advantages Simplicity: Easy to learn, easy to use, through documents and source code, you can completely grasp its design ideas and implementation. Practical： Provides data mapping capabilities that provide encapsulation of underlying data access (such as ado.net) and provides the Dao framework that makes it easier for us to develop and configure our Dal layer. Nimble: With SQL, you can basically implement all the features we can use without using the data access framework, or perhaps more. Functional integrity: Provides the connection management, cache support, thread support, (distributed) object management, configuration through relational mapping, and other data access layer issues that need to be addressed. Provides Dao support and encapsulates ado.net, NHibernate, and datamapper in the Dao framework. Enhancing maintainability of the system: By providing the DAL layer, business logic and data access logic are separated, so that the design of the system is clearer, easier to maintain, and easier to unit test. The separation of SQL from code improves maintainability. 2. disadvantages Hysteresis: There is no clear support for.Net2.0. The latest version can be compiled under 2, but some unit tests can not be passed. Immature and less engineering practice: IBATISNET is less used in real projects. Its only theoretically feasible Half ORM, less tool support: We need to write their own SQL, and.Net have not yet found the business layer and can automatically generate the tool profile, unlike NHibernate, NHibernate will provide our database directly to produce SQL, and some auxiliary tools. Therefore, using ibatis is a bit more work than nhibernate. 3. feasibility There is no best framework, only the most suitable framework. The existence is reasonable, and its existence shows the reason for its existence. But it does not exist for us. So, choosing a