BeanKeeper 2.6.3

BeanKeeper is a full featured, powerful object/relational persistence and query library for Java.

  Add it to your Download Basket!

 Add it to your Watch List!


Rate it!

What's new in BeanKeeper 2.6.3:

  • Simple to use. Read tutorial and begin to use it in minutes, no special tools required!
  • Zero configuration.
  • Small footprint.
  • Supports PostgreSQL,MySQL,HSQLDB,Oracle.
Read full changelog
send us
an update
LGPL (GNU Lesser General Public License) 
3.1/5 22
Robert Brautigam
ROOT \ Database \ Database APIs
BeanKeeper project was formerly called "Simple Persistence for Java" and is a full featured, powerful object/relational persistence and query library for Java.


Java enterprise software, and according to some, the Java language itself tends to go in the direction of extreme softcoding, or at least, in the direction of additional complexity. We've seen it happen with the EJB framework, and more recently, the Java Server Faces.

That does not need to be so! Other Java persistence frameworks such as Hibernate, TopLink or pBeans already are catching up to the philosophy of simpleness over "abstractness", however, we think there are more steps that can be taken in this direction.

From a developers point of view, especially in a high-level language such as Java, it is a sane assumption, that I do not have to (do not want to) get into the gory details of storing an object, I do not want to hold the database's hand on how to store my object, I do not want to tell it how to create approriate tables, columns, indexes, how to join tables, how to manage connections, how to allocate disk space, how to optimize queries, etc. I assume a "database" as such, should know how to do that without my help, that's why it's called "database".

So the point is, a good library should not get in the programmer's way, but adapt to the usage of the programmer, and adapt to patterns commonly used. This is what BeanKeeper tries to do. You don't need to (and you can't even) tell it how to store objects, it simply does. You don't need to specify the schema, relation model, id/key attributes, fetching algorithms, database dialect, or anything like that, you can focus on writing the business logic.


So how does all this philosophy stuff translate to a persistence software library? The library is not only supposed to handle all low-level database operations transparently, but also some of the more high-level functions. This must be done in order to enable the developer to concentrate only on writing logic.

Last updated on March 18th, 2010

feature list

#relational persistence #query library #Java library #BeanKeeper #object #relational #persistence

Add your review!