What about the argument “I just spent an entire day implementing the equivalent of a join and group by using my glorified key-value-pair library”? And what about the mantra “smaller code that does more”?
That’s a strawman argument. Why do we have to use glorified key-value-pair library when we can use sophisticated and powerful OODB ?
With OODB you do not need to implement joins because object graph works there just fine. And OODBs have indexes for a long time. It is not an exclusive feature of relational databases.
Now mind you, OODBs are very different from SimpleDB or CouchDB. And they perfectly fit for complex domains with very rich data hierarchy. Something relational databases handle very poorly.
That’s a strawman argument. Why do we have to use glorified key-value-pair library when we can use sophisticated and powerful OODB ?
With OODB you do not need to implement joins because object graph works there just fine. And OODBs have indexes for a long time. It is not an exclusive feature of relational databases.
Now mind you, OODBs are very different from SimpleDB or CouchDB. And they perfectly fit for complex domains with very rich data hierarchy. Something relational databases handle very poorly.