http://developer.db4o.com/forums/permalink/25969/26060/ShowThread.aspx Here is something interesting. Before I stumbled into db4o's highly
addictive ease of use and power. I briefly looked at Derby/JavaDB and
hibernate/Kodo JDO.
I suggested to a coworker to do the same thing.
Then, later on, I discovered db4o and asked the same coworker to evaluate it.
He first bulked, and resisted while trying to convince me with something like “Derby + Hibernate are a perfectly fine solution”.
Instead
of arguing with him, I asked him to show me what he liked about those
two products and to create a very small proof of concept using pieces
of the domain objects I had just created.
A few days later, he showed me a mini Swing application and the persistence code.
I
created something similar using Unit tests (real future production
code) instead of Swing and showed him how little code I had to write,
including a persistence layer-mini façade.
Yesterday, he confessed to his new addiction and asked me if he could include the db4o jar in the next build. I
explained to him that we are going to acquire a commercial license
(hardware vendor) in the near future and that we can’t distribute it to
our clients yet.
Not convinced with my answer, he asked our manager the same question and received a harsh and well-deserved reply.
This approach is mostly effective for small shops.
In our case, the savings are substantial even when you factor-in the
cost associated with acquiring a commercial license. I was forced to
eat elephants (http://tinyurl.com/2nmhv) for too long, but right now I love my chicken and db4o is one fine bird.
Aziz K.