Raven DB offers everything a developer needs in a document object database!
January 15, 2021

Raven DB offers everything a developer needs in a document object database!

Adam Nemitoff | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with RavenDB

I use RavenDB for all my projects that require data persistence. Document Store databases solve the problem of programming model/persistence model impedance. RavenDB has an amazing feature set that sets it apart from its competitors. The power and speed provided by its dynamic indexing makes writing complex and performant queries simple. And the focus on security and resiliency inspires tons of confidence. I have used RavenDB since v1 and with every release, it just keeps getting better!
  • The C# client makes using RavenDB feel like a natural part of the C# language.
  • Support is top notch! Even using free support you get speedy replies from engineers responsible for development of the DB engine.
  • The hosted cloud product is reasonably priced and makes it easy to deploy a resilient cluster with automatic backups.
  • I have never encountered any tasks that RavenDB could not handle.
  • RavenDB has decreased our time to market for new applications and features.
  • Development instances are essentially free reducing the cost per developer.
  • Operational costs remain low.
When I first started using RavenDB, I did evaluate Mongo DB but found it to be lacking. The primary issue was that Mongo DB did not support atomic consistency for the persistence of multiple documents at the same time, although I think this may not be an issue with subsequent releases of Mongo DB. If for some reason I were forced to select an alternative Document Database, I would probably evaluate PostgreSQL or CosmosDB.

Do you think RavenDB delivers good value for the price?


Are you happy with RavenDB's feature set?


Did RavenDB live up to sales and marketing promises?


Did implementation of RavenDB go as expected?


Would you buy RavenDB again?


For all the reasons I already stated.
Free support is good with engineers responding to technical questions.
Paid support is available with very good SLA
I suppose that if your data is flat and your schema is static, a Relational DB might be better suited.

RavenDB Feature Ratings

Data model flexibility
Deployment model flexibility