DB4O Object DB

Question

thinking of using an object db in memory, anyone have an opinion on DB4O?

Answer 1

I recommend highly DB4O and to support my vote DB4O was recognized as "Best of Open Source Software" at 2008 InfoWorld's BOSSIE Awards. This should count for something.

Answer 2

I had good luck using it with small databases (under 2 GB). My general feeling was that large databases would need quite a bit of tuning. To be fair though, that was quite some time ago.

As a product, db4o is well respected as a great product in the community. You can look at someone like Ted Neward who often promotes it to validate this.

I'd also suggest against using this as a server-side database. My primary experience was in using it as an embedded database for windows apps (i.e. very little concurrency).

Answer 3

Hi!

I'd strongly recommend using db4o for the following reasons:

• It's open source with great community support
• Native queries (strong typed)
• Ease of use and no additional work needed on the business layer side

Goran

Answer 4

Are there known problems or lack of testing with concurrency in the latest version? What is the opinion of the db4o dev community on the wisdom or otherwise of using db4o in a web scenario.

Answer 5

Re: Concurrency, would make a good separate question, but there is a discussion on the DB4o site: http://developer.db4o.com/Resources/view.aspx/Reference/Basic_Concepts/Concurrency_Control_And_Locking/Concurrency_Control_In_Db4o

Answer 6

If you are planning to store all the DB in memory, take a look at Prevayler. It claims to be very fast and reliable.