title: Azure DocumentDb vs RavenDb
body: <p>As .NET developers currently we're using <code>RavenDb</code> as our default choice of database, in the <code>nosql</code> scenario. Now that Microsoft introduced <code>DocumentDb</code>,  a <code>nosql</code> document database-as-a-service, we're looking for the differences between the two. Database-as-a-service does seems nice, as we run RavenDb on our own server. </p>
  
  <p>Ayende Rahien as an <a href="http://ayende.com/blog/168034/azure-documentdb" rel="noreferrer">interesting post</a>, but it's a little outdated as it compares with an old <code>DocumentDb</code> version. Nevertheless it's still a good read.</p>
  
  <p><strong>Edit:</strong> After reading <a href="http://nosqlguy.azurewebsites.net/azure-documentdb-thoughts/" rel="noreferrer">Thoughts on Azure DocumentDB</a> I started doubting <a href="http://azure.microsoft.com/en-us/pricing/details/documentdb/" rel="noreferrer">about the pricing</a> of <code>DocumentDb</code>. Let's say my data model consists of 7 collections, this means I would have to pay 7 * $25 = <strong>$175 per month!</strong> I must be making some kind of mistake here, right!? </p>
  
  <p><strong>Edit2:</strong> The idea of the creators of DocumentDb seems to put more than one type of document into a single collection, which seems a bit odd to me after using <code>ravendb</code> for a while now. The term <code>collection</code> caused some trouble understanding <code>DocumentDb</code> pricing as it is something completely different in <code>DocumentDb</code> then in <code>RavenDb</code></p>
  
  <p>In which scenario would you choose <code>DocumentDb</code> over <code>RavenDb</code>?</p>