Have you ever worked with a pure object data store? If you are using object oriented software, wouldn’t it be easier if your data store was object oriented as well? I’m not talking about NoSQL per se. It’s more along the line of a fully object compatible structure. I was running a google search out of curiosity for what is out there today and came across this web site that tests and ranks many different kinds of database engines in which you may be interested called DB-Systems: http://db-engines.com/en/ranking/object+oriented+dbms
I find it really amazing that there are so many different storage engines available commercially and in the open systems arena. Cache was at the top of the Object database ranking, and has been around since 1997. One of the things that set it apart from a lot of the newer object data engines is that it is not only object oriented, it also supports relational concepts.
Out of the box you get object capabilities with SQL built on top of it. That’s a little hard to get your head wrapped around. Think about a table where a column of that table may store another table. Pretty much like an object may contain a collection of other objects. Lots of power. Lots of flexibility. New ways needed to access this highly powerful data structure.
What are the hurdles you have found when trying to find or use object oriented databases? Are we ready for them today? Are the continuing NoSql data stored adequate for our needs? Are these systems relegated to high volume Transactions or Analytics only?
Share your thoughts with us in our comments.
Cheers,
Ben