tags:

views:

104

answers:

2

We are planning to use OO databases to store configuration objects. The options are:

 1 - Create 300+ relational tables.
 2 - Create a generic structure with few tables. We think this would 
make object relation mapping more complex to build and maintain.
 3 - Use a OO database. We are testing this now.

What do you think ?

A: 

Read mostly (or single user); simple relations; constrained object graph depth; constraint management non-requirement; and relaxed object identity use cases favor the oo db.

I think this is the case. And the size of the database will be small too. Just lots of attributes/fields and classes/tables depending on the choice
Marcelo Paes
In that case you can use an object db or one of the new trendy persistent key-value "db"s. Google Redis and (plug ;) JRedis on github and see if that works for you. (Also for a complete left field approach [;)], take a look at Lua. It was invented specifically to address configuration management in complex systems. Its claimed to be the fastest scripting language out there.)