Overall Satisfaction with RavenDB
Pros
- Excellent .NET support.
- Embeddable.
- Out of the box administration tools.
- Great documentation.
- ACID documents.
- Managed cloud available.
- Automatic indexes.
- Open-source.
Cons
- Time series data.
- Huge boost to productivity, we attempted to build our product two years ago taking around 9 months versus the 5 months for our current iteration. I can attribute this in significant part to RavenDB.
- Less time managing databases using the Cloud option, and a reduction in cost over AWS Aurora of around 30% for a similar server setup.
- Flexibility allowed us to rapidly build, test and greenlight two additional stretch goals we originally did not budget time for.
Amazon Aurora (MySQL)
- Expensive compared to RavenDB Cloud.
- Temperamental replication lacking a few features.
- No real document support and issues with cluster transactions.
- Lacks some killer features like distributed counting and document versioning.
- Expensive, even with the savings options.
- Not cloud agnostic.
- Not a perfect translation between JSON and DynamoDB's attribute system.
- Does not offer the same ACID guarantees as RavenDB.
- Poor query and indexing optimisation, tools and features.
- Lower performance.
- Lack of battle-tested transaction and ACID support.
- Poor indexing optimisation.
- AWS DocumentDB is quite expensive.
RavenDB Feature Ratings
RavenDB Support
Pros | Cons |
---|---|
Quick Resolution Good followup Knowledgeable team Problems get solved No escalation required Immediate help available Support understands my problem Support cares about my success Quick Initial Response | None |
Comments
Please log in to join the conversation