|
|
Browse by Tags
All Tags » db4o » Kudos (RSS)
-
''So db4o is in my view one of the simplest and most elegant data storage engines i have ever seen''
http://neilmartinagile.wordpress.com/2008/11/26/prototyping-new-wine-old-skins/
-
''I used db4o in my code because of the simplicity and native object storage. If you have never used db4o, I suggest it.''
by Jared on IOC Containers - Part 3
-
So Rob Conery wrote a really cool post the other day that I just had to comment on.
Here’s my thought for you: What if you used an OODB for development ONLY and implemented SQL Server later, when you know what you need to create.
It made me wonder; how many applications really, really need a full on RDBMS (Oracle, Sql Server etc.) ...
-
One of the things I've been working on was trying out the java persistence technology known as db4o.
My intention has been to find a database storage technology that handled hierarchical data well. Relational databases manage many situations very well but even the best ORM (Object Relational Mapping) solution tends to break down when handling ...
-
In his PureMVC web framework proposal Xavier Méhaut selects db4o as the persistence solution and says:
''I actually like DB4O a lot... It is fast and easy to use... Heaven in comparison with Hibernate ;)''
-
''db4o is my first choice for fast data storage, it can be set up in a matter of minutes and works great without any additional tuning. No more object-relational mapping to set up and maintain. I use it for embedded applications and as a replacement for existing providers in ASP.NET and ELMAH.''
Simone Busoli
-
''db4o is an excellent open source object database for Java & .NET platform by Carl Rosenberger's team. I highly recommend it for rapid prototyping and RAD. It transparently handles object storage and retrieval''
''In db4o you can create an complex objects with other objects as its member and db4o will save them all like a champ with a single ...
-
''...if you want to really increase productivity you can use the db4objects object database if that is a good fit for your type of application (your object model is the database!) saving you a lot of db to object and back transformation code''
Mike VanZanthttp://www.thestandard.com/news/2008/08/01/whos-afraid-big-net#comment-4039
-
[When it comes to db4o] by decreasing the complexity of the database a barrier to developers has been removed and in fact deployment is also made easier for the end user.
db4o [...] stores its data in a different way to a relational database. Rather than flat tables with repeated primary key and foreign key values splattered throughout, db4o ...
|
|
|