All object-oriented software developers are familiar with the difficulty transitioning from object-oriented thinking to relational persistence. The difficulty comes from the fact that the schema in the database does not match your application schema and you're forced to bridge that gap. Transformations between representations in memory and what goes to disk often take a good share of your cpu processing power. With an object database like db4o your application schema IS your data schema, no mapping required, no extra work (which translates into ease of use and higher performance!)

db4o Database Eliminates Complexity

The secret of db4o's success is its ease of use because it is native to Java and .NET, storing data objects exactly in the way they are defined by the application.  Therefore, db4o easily integrates into the application and no matter how complex your object models, performs highly reliable and scalable persistence tasks with as little as one single line of code. You are no longer required to predefine or maintain a separate, rigid data model, because the model is now created and updated 'on demand' by db4o itself during a transaction.

It's as easy as this: Drop db4o's single programming library (.jar /.dll), into your development environment, create a blank database file and store any object graph - no matter how complex - with as little as one line of code: e.g., in Java:

public void store(Car car){
    ObjectContainer db = Db4o.openFile("car.yap");
    car.engine(new TurboEngine());
    db.set(car);
    db.commit();
    db.close();
}

Done! db4o has created the data model during the transaction and now your object graph ( car and related turbo engine ) is fully stored. Even though this example might make you laugh, because it's so simplistic, you should note this is not serialization! Your object schema with any relationship is kept over time and is fully queryable and loadable into your application space independently, yet full connected!!

This unmatched ease-of-use results in drastically reduced development time and allows for efficient deployment. It eliminates the entire work and the constraints of (pre-)designing, implementing and maintaining the database schema, because the class model is the database schema. Even when deploying software updates, db4o's automatic schema versioning takes care that the software and the database are always in sync, while you can focus on building value-add product features!