Java Persistence Frameworks, again
Sheesh, this all looks complicated!
I'm looking for a persistance framework for a project if my own in the near future. David's post just makes me realize how little I know....
At work, we are using raw JDBC. I've been an RDBMS man for over a decade now, so JDBC 'fits my brain'. But it's time to learn to do persistance the OO way, if only so that I can make informed decisions. But which framework to choose?
Posted to Java by Simon Brunning at October 23, 2002 01:39 PMAt work we use cocobase by thought inc. for persistence. Nothing too fancy but it does what we want and then gets out of the way. Also the price was right, at least compared to toplink. We also have several layers of our own generated code (using xml and xslt) between the cocobase stuff and out business logic.
On the OSS side I've not really evaluated anything so couldn't comment.
Posted by: Alex Moffat on October 25, 2002 03:46 AMIt looks to me that Hibernate is the best choice given the consistent rave reviews I see on blogs and theserverside. It does not support JDO and I dont think it NEEDS to though it could improve acceptance. Though, I have not really used it, I plan to use it very soon. Good luck.
Posted by: bioye on January 20, 2004 08:21 AMWhy not use an object database? They in contrast to relational databases are designed to store objects!
There are several good ones that are open-source too:
GOODS and PERST: http://www.garret.ru/~knizhnik/
Ozone: http://www.ozone-db.org/
db4objects: http://www.db4o.com/
I've used GOODS and PERST - they really shine!
Posted by: Kavin Ging on March 10, 2005 08:04 PM