http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Object databases tend to be problematic because there is no really easy way to delimit an object graph. You are going to suffer from the same select n+1 issues that you see elsewhere, because it is so easy to traverse an object grapht hat is located on a remote machine. In documents, the model is self contained or another document, with no direct references between the two. We offer specific APIs to do set based updates. http://ayende.com/4797/ravendb-on-net-rocks#comment3http://ayende.com/4797/ravendb-on-net-rocks#comment3Fri, 01 Apr 2011 14:32:18 GMTAyende, What would be the pros of using a document database versus object database? Could you contrast the document database's approach to solving problems with relational databases versus how object databases approach to solve the problems? In the podcast, in an example you talk about demoralizing some relationships and storing things like customer name in the order document along with customer id? How expensive is it update all the orders for the customer in case his name changes? (if name is a bad example then customer's outstanding balance comes to mind) Thanks http://ayende.com/4797/ravendb-on-net-rocks#comment2http://ayende.com/4797/ravendb-on-net-rocks#comment2Fri, 01 Apr 2011 13:42:33 GMTLast paragraf of the bio made was made me laugh :) http://ayende.com/4797/ravendb-on-net-rocks#comment1http://ayende.com/4797/ravendb-on-net-rocks#comment1Thu, 31 Mar 2011 10:04:28 GMT