I don't think I've seen anybody ask the question. What if you used both OODBMS and RDBMS?
For the past couple years we at Kaivo have been working with Python and Zope. Typically we have been storing our data as objects in the ZODB (zope's object database). Also, recently we have been working with a company called Fresher who has just released a SQL Object Database called Matisse (http://www.matisse.com), which got it's roots in a French nuclear power plant some 12 years ago. We have the same struggles as everyone else. When should we store data in an object database, and when does it make sense to use something like Postgres?
Someone brought it to my attention that maybe object databases should be used as a middle tier storage platform, then the data could be pushed nightly (or weekly) to a relational database to be archived. Your application would access your current data in 'real time' directly from the object database cache, and could grab old data from the archived relational data.
Slashdot Mirror
I don't think I've seen anybody ask the question. What if you used both OODBMS and RDBMS?
For the past couple years we at Kaivo have been working with Python and Zope. Typically we have been storing our data as objects in the ZODB (zope's object database). Also, recently we have been working with a company called Fresher who has just released a SQL Object Database called Matisse (http://www.matisse.com), which got it's roots in a French nuclear power plant some 12 years ago. We have the same struggles as everyone else. When should we store data in an object database, and when does it make sense to use something like Postgres?
Someone brought it to my attention that maybe object databases should be used as a middle tier storage platform, then the data could be pushed nightly (or weekly) to a relational database to be archived. Your application would access your current data in 'real time' directly from the object database cache, and could grab old data from the archived relational data.