Overall Satisfaction with RavenDB
To start being ACID is vital for every Database. RavenDb is also easy to set up with advanced features included like a search engine with outstanding performance. Since Oren's team added graph support it's more delicious. In my country, all of my colleagues know that I insist all the developers leave the old RDBMS and switch to cool ones like RavenDB. Although most of them use MongoDB, which I don't suggest at all. In one sentence: On-premise or on the cloud RavenDb is my first, second, third, and so on choices.
- Cool clustering with modest features
- Fabulous auto indexing
- Great studio and dashboard
- Detailed documentation
- Attachments on the document
- Outstanding revisions
- Easy ETL
- Low prices on the clouds
- Multi model support
- Advance search
- Informative webinars
- High on-premise prices.
- Not a vast community.
- The fast deployment helped us on our MVPs.
- Fast setup helped us on our pipelines.
Being that ACID and cluster transaction support is a big plus against all of them. Cool prices on Azure and AWS is another plus. The ability to search between millions of documents.
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
RavenDB Feature Ratings
Using RavenDB
2 - BI/DBA on market and different products
- Get rid of ORM's
- Easy to deploy
- Need of deep chart types
- Add other search types
- Use on our monitoring using Time-Series
- Deploy on the cloud
Evaluating RavenDB and Competitors
Yes - MongoDB. It's not ACID and has a poor design in spite of its large community.
- Price
- Product Features
- Product Usability
- Prior Experience with the Product
The Price of the RavenDB on cloud makes sense.
Look at the product models and redesign them to reach the best model. Revise the organization products architecture to reduce the different type of Databases with different usages. Research carefully on the AI future of the product and choose the right database to support them all or most of them together.
RavenDB Implementation
- Implemented in-house
Change management was a minor issue with the implementation
- Used repository in the very first years, but after a while learned to expose the DocumentSessions to write specific queries based on the usage.