Started new project with RavenDb, and some experience: - no need for ORM tools. Finally. I was little tired from Nhibernate, EF, and their's complex mappings.

Started new project with RavenDb, and some experience: - no need for ORM tools. Finally. I was little tired from Nhibernate, EF, and their's complex mappings. They are great tools, but not for every project and scenario. - fast dev: simple or almost no configuration. Just point your code (raven session) to server URL - safe by default: most of linq queries works just fine, dynamically created indexes - hosting option: start raven .exe, host it in web app from subfolder/subdomain, use embedded db (it took me some time to configure web app hosting, but there should be some good docs now, i hope, because it's simple) - nice management tool for testing queries, inspecting docs, etc. - had problem with reading docs in Silverlihgt that are stored in web app, because some problem with JSON serializer. Had to give up from raven for that project - still struggling with creating Map/Reduce indexes in practice, there's no many samples - no sample apps - hard to make mind shift from relational thinking, it should be closer to object/domain model, but we are corrupted with years and years of relational data and joins. Most of our domain object model is really not object oriented model So, I'll definitely try it on some next not-critical project. There are scenarios for which raven, or any other doc db, is great, and that doesn't have to be "100-db/web server installation web startup", I think it's just fine even for small projects.