http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660cs, I'll try to add something about this to my queue for blogs.http://ayende.com/126977/steamlining-ravendb-part-ii-why-ravendb-lazy-requests-are-in-the-advanced-section#comment6http://ayende.com/126977/steamlining-ravendb-part-ii-why-ravendb-lazy-requests-are-in-the-advanced-section#comment6Wed, 26 Oct 2011 14:01:35 GMTAyende, can you expand on your answer to Frank's question? What other scenarios would you choose a RDBMS over RavenDB? I'm new to NOSQL, and I'm currently struggling with trying to figure out how to identify which scenarios Raven would be used instead of NH+SQL. Thanks!http://ayende.com/126977/steamlining-ravendb-part-ii-why-ravendb-lazy-requests-are-in-the-advanced-section#comment5http://ayende.com/126977/steamlining-ravendb-part-ii-why-ravendb-lazy-requests-are-in-the-advanced-section#comment5Mon, 24 Oct 2011 18:54:41 GMTIn general terms what you expect when using the RavenDB API is what you get. That was my case except for DocumentQuery being mutable, which can be frustrating until you get to know it. +1 for keeping it simple. http://ayende.com/126977/steamlining-ravendb-part-ii-why-ravendb-lazy-requests-are-in-the-advanced-section#comment4http://ayende.com/126977/steamlining-ravendb-part-ii-why-ravendb-lazy-requests-are-in-the-advanced-section#comment4Mon, 24 Oct 2011 13:29:41 GMTAyende, I really like your choice of keeping the API very simple. Everything beyond CRUD should go directly to Session.Advanced or instead be implemented as an extensions method. That way it remains easy for new developers to understand existing code. Keep on that great work!http://ayende.com/126977/steamlining-ravendb-part-ii-why-ravendb-lazy-requests-are-in-the-advanced-section#comment3http://ayende.com/126977/steamlining-ravendb-part-ii-why-ravendb-lazy-requests-are-in-the-advanced-section#comment3Mon, 24 Oct 2011 13:11:53 GMTFrank, Usually, reporting scenarios are a good candidate to use a relational DB rather than a document onehttp://ayende.com/126977/steamlining-ravendb-part-ii-why-ravendb-lazy-requests-are-in-the-advanced-section#comment2http://ayende.com/126977/steamlining-ravendb-part-ii-why-ravendb-lazy-requests-are-in-the-advanced-section#comment2Mon, 24 Oct 2011 12:12:44 GMTHere is a tangential question which I wanted to ask for a while. In what situations would you actually consider a RDBMS to be the better choice as opposed to using a Document Database? Since you are pushing the envelope on RavenDB, you may not be the best person to ask, but you've used NH + SQL in earnest, so maybe there are scenarios where you would choose e.g. SQLServer over a Document database?http://ayende.com/126977/steamlining-ravendb-part-ii-why-ravendb-lazy-requests-are-in-the-advanced-section#comment1http://ayende.com/126977/steamlining-ravendb-part-ii-why-ravendb-lazy-requests-are-in-the-advanced-section#comment1Mon, 24 Oct 2011 11:48:43 GMT