Our main goal is to provide a newsreader that is powerful, easy to extend and easy to use. We chose the Eclipse Rich Client Platform as framework and db4o as powerful database to store all the news. In combination with the well-known full-text search engine Lucene, we are able to implement exciting new features.
http://www.rssowl.org/node/210
The db4o micro commercial offering allows you to use db4o in software that runs on handheld devices at a unit cost as low as a a dollar. If you plan to ship tens of thousands of copies of your software, that is a pretty good price. The market for software that runs on handheld devices is huge. Vendors of handheld hardwre are finding it harder to differentiate themselves based on hardware; therefore, the differentiator is software. db4o has been very reasonable in their pricing, and I think this represents a huge opportunity for them. That was smart!
http://jimcassidy.ca/2007/02/22/a-good-deal
The current problem with ODBMS systems is just that basic business intelligence or even reporting is quite difficult with them. Anyway I think db4o is one of the greatests pieces of software out there for OLTP-only systems.
I strongly believe that seperation between domain og model is best achieved by a data access layer designed for the specific application. Implementation of such a layer should be replaceable!Implementation of such a layer could be done using an ORM. That oftens makes good sense. However, there is an alternative. Why not choose a database that match your model? Why not choose an ODBMS?I think there is too much focus on ORM tools. Go take a look at alternatives such as http://db4o.com. If you still feel you need a ORM, fine. If you don't. Congratulations, you saved yourself a lot of work and probably some money too.
Something I really like about db4o is the "ease of deployment."Drop the db4o-jars to your project, define a suitable location for your database file and just start working...A very nice productivity factor comming along with db4o: It's so easy to work with a copy of the production database on your development machine. Just copy the original (or backuped) db4o-yap-file and start your application on the development-machine. That's it!
http://db4o.blogspot.com/2007/02/no-more-fakes.html
As I contemplate all of the tools out there, including Oracle’s Berkeley DB, I notice that everyone is bragging about unattended execution, or zero administration. Nobody loves the poor old DBA. My choice for an embedded database would be DB4O. DB40 provides the means to query the database. The product is much faster than a version played with almost 2 years ago, but the selling feature for me is that the product provides the means to query the database using objects. I am looking forward to looking at LINQ when it becomes available, but DB4O is not tied to the .NET framework - it works in Java as well as .NET, and it can run on Linux.
http://jimcassidy.ca/2007/01/29/lets-fire-the-dbas/
http://www.dotnetguru.org/modules.php?op=modload&name=News&file=article&sid=874
DNG n'avait jamais eu l'occasion de mettre en lumière Db4o, c'est aujourd'hui chose faite. Ce projet OpenSource a pour objectif de fournir une base de données nativement orientée objet. Les bases de ce type seront inévitablement amenées à se développer dans les années à venir avec la montée en puissance (et les premiers écueils) du mapping objet/relationnel. Db4o possède de nombreux atouts que sont sa mixité technologique (support de .NET et Java), l'originalité de son modèle économique (Open Source Professionnel) et la qualité de son équipe de développement. Il est peut-être temps de franchir le pas du SGBDO...
http://www.gregwhitescarver.com/blog/2007/02/03/object-persistence/
I’ll be keeping my eye on things like db40 to see if workable object persistence ever makes its way to PHP land.
A future where SQL and relational databases are arcane tools used primarily by the minders of legacy systems is conceivable. As OO takes over more and more of the software space, and servers get faster and faster, the potential savings in development costs offered by real object persistence will outweigh the speed penalty.