RavenDB user since the first version
Updated July 21, 2020

RavenDB user since the first version

Wallace Turner | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with RavenDB

RavenDB is being used to house downstream trading data from an exchange. The data must be extremely fast to access and highly available (no downtime).
  • Feature rich .NET API.
  • Simple setup for clustering/high availability.
  • Fast document access via auto indexing.
  • Own language for querying (RQL) not usable elsewhere
  • learning curve for stale documents/eventual consistency
  • Not having to debug perf issues caused by ORM.
  • Not having to deal with SQL as you denormalize your app data model.
RavenDB has a richer API, has security out of the box (via certificates), produces indexes automatically and updates them when data changes.
It currently 'ticks all the boxes' for all our use cases - I also use the free tier in a number of personal & commercial projects - it is the only product I know that provides a HA solution freely. The RavenDB Support (both paid and google groups) is very active and responses are timely.
RavenDB is useful for providing high availability (HA) which we achieved by clustering across physically different servers.

RavenDB would not be appropriate if you have dynamic queries - e.g. where the fields being queried are not known ahead of time and thus indexes would have to be built on all fields (or dynamically as required).

RavenDB Feature Ratings

Data model flexibility
Deployment model flexibility