+972 52-548-6969
RavenDB on .NET Rocks
time to read 1 min | 69 words
Carl and Richard talk to Oren Eini, aka Ayende Rahein, about RavenDB. RavenDB is a NoSQL JSON document database. Oren explains how he came to the realization that he needed to build his own data store, and the advantages of document databases over relational databases. Is SQL dead? Not hardly, but RavenDB is an interesting addition to your data solution!
You can listen to it here.
Comments
Last paragraf of the bio made was made me laugh :)
Ayende,
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
Object 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.
Comment preview