In search of a better persistence API(摘)

王朝java/jsp·作者佚名  2006-01-09
窄屏简体版  字體: |||超大  

60% JDBC

20% Homegrown Persistence Framework

10% O/R Mapping Tools

5% Java Data Objects (JDO)

5% EJB CMP / BMP

0% Service Data Objects (SDO)

Considering that ORM only has 10% of the market, and "seldom is a good choice in systems typically with very large dataset and complex queries" one can wonder what the fuss is all about?

Why not settle for a common abstraction layer and let each run according to own taste. It should be obvious by now that it is never going to be any consensus between the different persistence camps.

One big advantage is that it will not be necessary to frisk for weapons at the entrance to conferences and seminars! :)

Yi Zhou:

"I propose a cohesive persistence layer based on Spring Persistence Layer"

The obvious solution. (Think logic, reason, common sense. Exist for both Java and .NET) Can anyone imagine how much money that could be saved by this approach? All over the world?

Unfortunatly there is never possible to settle for anything obvious as long as a committee is involved.

Regards

Rolf Tollerud

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
 
 
© 2005- 王朝網路 版權所有 導航