Kudos

[Kudos] db4o is the easiest persistence thing i have ever used

German Viscuso — Fri, 06 Nov 2009 13:23:00 GMT

From Twitter:

RhysC : HOLY CRAP.... DB4O is the easiest persistence thing i have ever used. Zero set up. Its insane! #DB4O #FTW!!!

xinmyname : The more I work with db4o, the more I love it...

[Kudos] db4o: Simplest approach I've seen so far. And above all, it's fast!

German Viscuso — Tue, 03 Nov 2009 15:49:00 GMT

Database for objects. (forget OR-Mappers, forget 2D relational data representation)
Γαμάτη υλοποίηση για αποθήκευση δεδομένων ως objects. Δηλ. object oriented database ;-)

Την έφερε στην προσοχή μου φίλος και τον ευχαριστώ ! Πιο απλή προσέγγιση στο θέμα δεν έχω ξαναδεί. Και πάνω απο όλα ΤΑΧΥΤΑΤΗ !!

Kudos στο project http://www.db4o.com

http://proteasdevelop.blogspot.com/2009/11/db4o.html

[Kudos] There's no going back

German Viscuso — Fri, 11 Sep 2009 16:31:00 GMT

"I realized today that I can't go back to Relational Databases after using db4o"
http://twitter.com/alosii/status/3902468119

[Kudos] db4o is freekin' AWESOME!

German Viscuso — Tue, 08 Sep 2009 01:16:00 GMT

"The beauty of [db4o] is that there is NO mapping code since it's just serializing the objects. NONE! [...] Add a property? No changes needed, it just "works"... Yep the test passes! Sorry people, but that's freekin AWESOME!"

Elliott O'Hara in "Meddling with Object Databases (Db4o)"

[Kudos] db4o's design dramatically reduces the learning curve and makes it a pleasure to use

German Viscuso — Wed, 05 Aug 2009 12:01:00 GMT

In "Progressive Disclosure in API Design with example":

"db4o's API implements this paradigm perfectly in several places. The basic ObjectServer, for example comes only with methods to grant access, open or close a client. It provides an ext() method which provides access to ExtObjectServer, with less frequently used methods. In previous versions db4o object similarly provided access to ExtDb4o object for extended features. This particular design of db4o dramatically reduces the learning curve and makes it a pleasure to use in my experience.
To know more about db4o read our guide to learning Db4o, Java Object Database, in under 5 minutes. Also look into couple of tricks and gotchas with Db4o."

Angsuman Chakraborty, Taragana.com

[Kudos] Loved this db4o demo. Crazy awesome. 10 levels above awesome

German Viscuso — Tue, 28 Jul 2009 17:11:00 GMT

Comment in "A Domain Driven Rich Internet Application using Silverlight 3, RIA Services and DB4O"

Loved it. I'm tearing the example apart figuring out what's going on there.
Crazy awesome. 10 levels above awesome.

-- Justin Angel
Microsoft Silverlight Toolkit Program Manager

[Kudos] db4o: pain free development

German Viscuso — Mon, 29 Jun 2009 10:23:00 GMT

"Versant have come up with an easy to use object-database.
Next to using relational databases, development is pain-free"

http://we-fearless-ones.blogspot.com/2009/06/db4o-object-database.html

[Kudos] I hope db4o gains more and more traction

German Viscuso — Thu, 25 Jun 2009 17:04:00 GMT

"db4o is an object database which means there is no mapping files, attributes or other ‘impedance mismatch’ between your c# classes and the ‘database’ itself. It’s mostly used in embedded scenarios but appears to be getting used in websites. I’ve only just scratched the surface with it here, but i think it’s very cool and i hope it gains more and more traction."

Keith Patton

[Kudos] db4o is easy, you just store your native objects, done

German Viscuso — Fri, 17 Apr 2009 07:16:00 GMT

"I've found the object-database db4o, which fits my requirement perfectly. It is really small, less than 800 KB. It is easy, you just store your native objects, done. Retrieving the objects is also easy, because db4o supports LINQ"

http://www.gamlor.info/wordpress/?p=332

[Kudos] db4o: the answer to all my prayers

German Viscuso — Thu, 26 Mar 2009 23:05:00 GMT

When I first found db4o a year ago, I was, and still am, convinced that it answered all my prayers regarding the true object-oriented model.

Brian Blockhart in "Pushing the db4o Limits"

[Kudos] Turn your back on Hibernate and all things RDMS and go ahead developing with db4o

German Viscuso — Thu, 26 Mar 2009 09:32:00 GMT

Well, I've finally decided to turn my back on, at least for the present time, Hibernate and all things RDMS, and go ahead developing with db4o and OODB.

So, why the switch? Lets just say that I like having as little between me and my objects (of desire) as possible. I like being able to store my objects in one line of code, and retrieve them almost as cleanly. Plus, DB4O is it's own API and DB in one jar - which goes a long way towards avoiding the jar bloat you'd face if you wanted to ship your app as a standalone ear / war, especially compared to Hibernate (even more so if using Annotations > Validator > Entity Manager).

Charles Burrell

[Kudos] With db4o's LINQ support the DB looks as an advanced collection in memory (in Norwegian)

German Viscuso — Sun, 22 Mar 2009 05:02:00 GMT

Through Linq, I can express exactly what I want. I can work with the database as if it were an advanced collection in memory, and get back my own domain objects without having to make some form of mapping. Working with persistert data has never been easier!
(in Norwegian)

http://blog.kjempekjekt.com/2009/02/27/objekt-orienterte-databaser-del2-db4objects
(automatic translation to English)

[Kudos] db4o: non-intrusive, very simple to learn

German Viscuso — Mon, 16 Mar 2009 08:10:00 GMT

db4o is a popular object database available both for Java and .NET. I have used it sporadically over several years and can highly recommend it. It is a non-intrusive, very simple to learn, object persistence system that stores any complex object with one single line of code. Unfortunately Db4o is still not as popular with Java developers as we thought it would be. So we thought of giving you a very easy and useful guide to learning db4o.

http://blog.taragana.com/index.php/archive/how-to-learn-db40-java-and-net-object-database-in-5-minutes

[Kudos] db4o is extremely portable

German Viscuso — Mon, 16 Mar 2009 01:49:00 GMT

After all of the griping that I have done regarding DB4O, I would now like to say a few positive things about it. I am planning on replacing Hibernate with it, due to the fact that I just don't like "Jar Bloat" which can turn into "Dependency Hell" if not managed carefully. DB4O is a neat tool,

It is extremely portable. Unlike Hibernate, there is only a single jar file (no dependencies), and you don't need an external DB, even a Java Based one such as H2 or HSQL

It makes saving objects an almost trivial affair. Retrieving objects is (depending upon the method you use) is not that much harder, and updating and deleting objects are very easy operations too - in line with Hibernate. I prefer to use Native Queries for my updates and deletes because I can match my objects exactly a bit easier, and SODA for retrieving my objects.

Lastly, it's fairly fast. Not nearly as fast as straight SQL (but then again, what is?), but on par with Hibernate for simple CRUD, and a bit slower for mass stores / retrievals.

Charles Burrell

[Kudos] db4o on shared hosting love

German Viscuso — Wed, 11 Mar 2009 23:40:00 GMT

I'm tired of fighting the ORM battle, L2S, SubSonic, NHibernate, Lightspeed, etc. They're all great products but painful to use because they are all "bandages" on the problem of object-relational impedance. So I thought I'd try something different, db4o. db4o is an object database. No tables, no ORM, nada. Just POCO love, it's like the repository pattern on steroids (but not the shrink your package kind, the good kind). My big concerns were licensing costs and the fact that I deploy on a shared host. Both of which were misplaced.

The licensing cost for an In-Process database for commercial use was comparable to a standard ReSharper license. So it's within the reach of "normal" developers who'd like to use the database for their web application. If you're writing an open-source application or one that is not for redistribution, then the GPL license will be fine for your purposes. Honestly, I was expecting thousands of dollars for the licensing, as the technology is so impressive.

After finding out that the pricing was within reason I was excited but afraid that it's all well and good that I can afford it but I'm using shared hosting, so it's going to be impossible to deploy. Wrong again! The In-Process database only requires a single DLL to function. Let me reiterate that, the entire db4o system is contained in a *single* library that only requires medium trust and the ability to write to a file. So I used some of the demo code provided by db4o and whipped up a little POC to see if this would work on my ReliableSite.net account.

http://just3ws.wordpress.com/2009/03/11/db40-on-shared-hosting-love/