RavenDB user since the first version
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).
Pros
- Feature rich .NET API.
- Simple setup for clustering/high availability.
- Fast document access via auto indexing.
Cons
- 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.
Comments
Please log in to join the conversation