If you need read performance or abstraction from a datastore look no further.
Overall Satisfaction with RavenDB
I use RavenDB as a developer and a software architect on pretty much every project that requires data storage. Mostly its consumer-facing applications that require rapid response times [need some work]. It's very quick to develop with and we get awesome read performance from it which is why we use it. It is also easy to maintain.
Pros
- Easy to implement an Event Sourced Architecture
- Very rapid response times
- Highly abstract to enable smart design
Cons
- Large scale complex data updates can be painful
- Finding people who know how to use it and appreciate it
- Doesn't support direct GraphQL (yet)
- Cheap hosting through Raven Cloud makes it affordable
- Much faster development
- Easier to design smarter systems
- Nightmare getting clients to adopt it because it's not well known
[RavenDB is] just simply much cleverer than the competition. The map reduce indexing is a league above anything else I have used. Nothing else comes close on abstraction as well. Read performance is terrifying due to querying pre calculated indexes. It is just a pity it is not better known and that more people haven't adopted it.
Do you think RavenDB delivers good value for the price?
Yes
Are you happy with RavenDB's feature set?
Yes
Did RavenDB live up to sales and marketing promises?
Yes
Did implementation of RavenDB go as expected?
Yes
Would you buy RavenDB again?
Yes
Comments
Please log in to join the conversation