orm – Why have object oriented databases not been successful (yet)?

orm – Why have object oriented databases not been successful (yet)?

The main reason is SQL. It is very useful to be able to use the data from a database in other contexts outside of the application, and often with object databases the data is stored in a format that cant easily be queried. With a relational database the data can become part of a data warehouse, for instance, or just queried by sys admins etc.

Can we answer more than once? Another reason is that relational DBs have a strong foundation in mathematics: from the definition of a relation, right through to the normal forms, the theory is rock solid. It is true that the relational model does not map well to OO, but IMHO the benefits and stability of that model outweigh the mapping problem.

orm – Why have object oriented databases not been successful (yet)?

I think its because object databases are solving a problem that (almost)nobody really has. For simple persistence of object graphs, the serialization built into most OO environments is good enough. If you want to do sophisticated operations on a subset of your data, then a relational database and SQL are a perfect fit.

Other than some fringe applications (enormous object graphs that cant be kept in memory, but for which the relationships dont simplify down well for RDBMS use), there really isnt any need for these tools.

Leave a Reply

Your email address will not be published.