Kudos

[Kudos] db4o works like a champ

German Viscuso — Wed, 20 Aug 2008 22:32:00 GMT

"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 set() (now store()) method"

Angsuman Chakraborty's blog post

[Kudos] Increase your productivity with db4o

German Viscuso — Thu, 07 Aug 2008 09:22:00 GMT

"...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 VanZant
http://www.thestandard.com/news/2008/08/01/whos-afraid-big-net#comment-4039

[Kudos] Dead simple

German Viscuso — Wed, 11 Jun 2008 18:40:00 GMT

[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 uses a different model. It builds upon the popular object oriented programming paradigm which will be familiar and comfortable to those who code in C++, Java, Smalltalk, Python and even, on the Windows side, Visual Basic.NET, Delphi and more.

What makes it special are several abilities so cunning you could pin a tail on them and say it’s a field of weasels.

db4o will save slabs of memory to disk with a minimum of fuss.

I am certain you will agree this really is a no-brainer to work with. And yet, it’s not a trite system either. Database experts will be interested to know if db4o offers multi-threading, flexible indexing, atomic transactions and other such things. The answer to these is yes; it is high performance and maintains integrity of its data. db4o does not offer stored procedures but that’s not really an issue; the focus turns back onto putting code within the program and leaving the database to just store data.

If you’re a developer, no matter the platform, give an object database a try and see how it can revolutionise your coding, as well as pave the way for more developers to come across to Linux.

http://www.itwire.com/content/view/18714/1141/

[Kudos] db4o helps blur the lines of application development and database development

German Viscuso — Sun, 18 May 2008 09:12:00 GMT

"Embarcadero Technologies’ acquisition of CodeGear and the announcement of db4o’s support of LINQ are more evidence of the blurring of the lines of application development and database development. Increasingly, application developers want and need better insight and control of the data management aspects of their applications. On the flip side, database administrators are faced with responsibility of ensuring application performance. Common toolsets and better communication can only help both communities achieve their objectives."

Gregory Keller
VP-Product Management at Embarcadero Technologies, Inc
http://metafrequency.blogspot.com/2008/05/train-is-movin.html

[Kudos] LINQ for db4o is extremely easy to use and very powerful

German Viscuso — Tue, 29 Apr 2008 19:31:00 GMT

LINQ for db4o is extremely easy to use and very powerful. The learning curve is very low. This publication only scratched the surface of the possibilities of db4o. If you are trying to compare it with the RDBMS that you now use then you definitely have to take into consideration that:

The performance is very good. According to this benchmark its one of the best.
All work within db4o ObjectContainer is transactional. (Manual rollback and commit are available.)
The replication tool for db4o makes db4o scalable.
The db4o database can be accessed in Client-Server mode. This can be done using an embedded Client-Server or a Networked Client-Server.
There is an object manager tool available for browsing and querying a db4o database. Although you can't build queries with the free version its a nice tool for browsing your database.
You can control Concurrency and locking.

Edwin Vermeer
Senior Software Developer
Mirabeau B.V.
The Netherlands

[Kudos] Query support in db4o is more powerful than in Ehcache

German Viscuso — Wed, 26 Mar 2008 18:53:00 GMT

At last, I decided to apply DB4O to our project. One important reason is that this strategy lets programmers write code in high level. I don't need to care about any details of database infrastructure. As a result, modification of my original code is little so that it can be done quickly. Moreover, maintenance of code is easier. We store both data and related operations in database instead of scattered places. What's more, support of query is more powerful in DB4O than in Ehcache. It supports three kinds of query languages: Query By Example, Native Queries and SODA. And complex query can be composed easily.

by Gerald Guo
http://zhenhua-guo.blogspot.com/2008/03/state-information-persistence-status.html

And a simple db4o introduction by the same author:
http://zhenhua-guo.blogspot.com/2008/03/db4o-introduction.html

[Kudos] db4o, the right place for you

German Viscuso — Mon, 24 Mar 2008 17:16:00 GMT

"I got the impression that everyone at db4o really likes what he/she is doing. Every fixed bug or new feature is rewarded with a "virtual tap on the shoulder" by the other team members. And people are not afraid to admit that they made mistakes, because every found/admitted mistake is one that can be fixed."

"If you are interested in working in a small company with motivated people in an open source community environment from wherever and whenever you want, then db4objects could be the right place for you!"

Christoph Zimmerli (dVP and former db4o intern)

[Kudos] Developers can focus on the domain model and the value-add code, rather than data persistence

German Viscuso — Thu, 28 Feb 2008 13:27:00 GMT

If you are not familiar with db4objects ( DB4O ), it is an object oriented database. What does that mean? If I boil it down in laymen's terms : it is a database without tables or columns.
[...]
I did not have to do anything to setup how to save a User object in the database. It just serializes the object to the database. No need to worry about table names, column names or data types. This all comes for free with this engine, allowing a developer to focus on the domain model and the value-add code, rather than data persistence.
[...]
To help facilitate getting to software that can be demonstrated, I think that using a persistence engine like DB4O could really help with the time to delivery.

http://lostechies.com/blogs/hex/archive/2008/02/26/using-db4objects-as-a-prototyping-tool-part-i.aspx
(includes db4o related source code)

[Kudos] LINQ for Java should look a lot more like db4o than Quaere

German Viscuso — Tue, 26 Feb 2008 00:26:00 GMT

LINQ for Java should look a lot more like db4o than Quaere. An independent project to do something like db4o's native queries would be nice. Maybe sit on top of JPA for ORM, or something like that.

http://tomobag.blogspot.com/2008/02/linq-for-java.html

[Kudos] Database access made stupidly simple

German Viscuso — Mon, 18 Feb 2008 11:09:00 GMT

Last time I had to develop a standalone application which would rely on a database, I had to design the whole data model, deploy it into a RDBMS, implement DAOs for CRUD operations and, only then, implement my business logic.

Nowadays, things are so easily made that any dumb ass with access to Google and a Java/C# compiler can do that in no time (RoR developers, stop your urge to coment right here, please)! With C# or Java and db4o [..] you can forget data modelling and deployment and go directly for code development. Just create your classes, and start implementing your business logic.. Your database will be magically generated, deployed and persisted!

So, you have almost for “free (as in code)” the following capabilities:

Persistence;
Transactional operations (ACID);
Object-Oriented querying;
Standalone or Client/Server environment;
Minimal footprint;

I recommend everyone, even the ones developing enterprise applications to give some time to these technologies. Perhaps you’ll learn something about flexibility and easiness.

Full post: http://ppires.wordpress.com/2008/02/14/database-access-made-stupidly-simple/

[Kudos] db4o is as transparent as I imagined data storing should be

German Viscuso — Fri, 08 Feb 2008 05:35:00 GMT

“I like db4o because it has a very simple API, a small footprint but also allows dealing with complexity. It is as transparent as I imagined data storing should be.

There is no need to modify your domain classes at all.”

Gerd Klevesaat
(Author of Eclipse and NetBeans plugins for db4o)

[Kudos] With db4o your data IS an object, not a flat representation of an entity

German Viscuso — Thu, 17 Jan 2008 03:50:00 GMT

Today I spent the majority of the day wrestling with an ORM tool, and I didn't get very far, and as a result I don't like my job very much right now.

This is a particularly painful mark on my workplace happiness because of the very positive experiences I've recently with DB4O, so I'm going to compare and constrast a little bit to vent my pain... [check the post below for the actual comparison]

http://codeclimber.blogspot.com/2008/01/relational-vs-object-oriented-databases.html

by Ethan Vizitei

[Kudos] The incredible simplicity of db4o hit me immediately

German Viscuso — Mon, 14 Jan 2008 19:52:00 GMT

...I took another look at db4o, a pure object store for Java and .NET. It did not take me long to realise the advantages for small projects. Java code to open a store and save an object consists of only a few lines, and with no need for mapping or any kind of “instrumentation” of classes; at least not just to get going or for small applications. I decided to try this using Groovy.

The incredible simplicity of this hit me immediately. Suddenly all those paragraphs of instructions about how to set up different databases for RoR, and all the rules of how to configure different types of relational connections beteen classes looked very tedious, especially as Rails was supposed to be the great time-saver.

So, I am going to start a long-term project, that I will report on here. The aim is to see how simple Grails could be with an object database; without the use of Hibernate or JPA; without ORM at all.

Steve Zara and Jonathan Harley, directors of UK software consultancy company Zac Parkplatz Ltd.

http://www.jroller.com/ThoughtPark/entry/rails_and_grails_without_the

[Kudos] db4o combines smoothly with Struts 2

German Viscuso — Tue, 01 Jan 2008 23:32:00 GMT

Anyone here using Db4o as a persistence solution with Struts 2? I have a couple of S2 sites running over this object database, and I have never had such a smooth job of developing code. I only had to think about one thing -- objects! No mapping files, XML, table names, join strategies...

Holla back if you have similar stories to share

Scott Stanlick (Manning Publications Co. Author)

http://www.manning-sandbox.com/thread.jspa?threadID=22193

[Kudos] Flex + LCDS + db4o = truly rapid development

German Viscuso — Thu, 06 Dec 2007 05:45:00 GMT

The main thing I've been up to recently, outside of regular working ours, is getting up to speed with Flex and LiveCycle Data Services.

I have to say, Flex combined with LiveCycle Data Services using db4o is absolutely the fastest way I've ever created an internet application with full data support in the back end. Flex itself makes UI development a doddle. LiveCycle Data Services make accessing data in the back end as simple as called methods on a POJO (real POJOs), then combine this with db4o so that you don't have worry about RDBMS issues and you're really flying in no time.

Flex + LCDS + db4o = truly rapid development

Chris Brind (referring to Rapid Rich Internet Application Development)

http://techy.brindy.org.uk/2007/11/i-havent-blogged-for-short-while-so-i.html