RavenDB is the future of databases and everyone should be using it!
July 28, 2021
RavenDB is the future of databases and everyone should be using it!
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with RavenDB
RavenDB is being used as a central database for many applications. We also use it as a caching server in some instances. RavenDB has a feature for every need we seem to come across. When a new problem comes up, RavenDB usually will have a built-in feature to solve our problem, and we don't have to write custom services to solve it. It plays a central role in all the applications I work on. Since RavenDB uses a distributed model, we are able to add new cluster nodes and scale out instead of up. This makes it flexible for a small app getting started that can grow into something very large and not have to worry about your database being able to handle the traffic.
Pros
- Speed
- Features
- Support
Cons
- The documentation is very good, but it's sometimes hard to find the topic I'm looking for.
- Updating references is done manually. It would be nice if there was a feature to help with that. I'm not sure that's even possible though.
- RavenDB has saved my customers a lot of money with their cloud services' tiered model. The database is able to grow with the project/company and can start out small at a low cost.
- RavenDB is free for three nodes and three CPUs, which makes it great for development scenarios. You're able to start rapidly building applications without having to worry about licensing.
- Scaling out has allowed us to use three small cloud servers when starting out and get the performance and throughput of a single larger server.
Having ACID compliance is a big enough reason to choose RavenDB over the other products. You don't have to worry about losing your data if the plug is pulled. You're able to perform many actions within a transaction and not worry about your data being in a bad state if the transaction fails. It has all the great features of a traditional SQL database, but in a NoSQL document store.
Stability is another great reason. ACID ensures data integrity. Having a cluster of nodes that talk to each other ensures availability if a node goes down and also allows for a lot more traffic to make queries.
RavenDB also has an amazing studio to work with. The design is excellent and pleasing to the eye. You are able see everything that is going on in the system. You can view and edit documents directly or through scripting patches. You can even edit internals if you really know what you're doing. The best part is the studio just uses the RavenDB API, so anything you see in there you know is possible to do yourself with a client library.
Stability is another great reason. ACID ensures data integrity. Having a cluster of nodes that talk to each other ensures availability if a node goes down and also allows for a lot more traffic to make queries.
RavenDB also has an amazing studio to work with. The design is excellent and pleasing to the eye. You are able see everything that is going on in the system. You can view and edit documents directly or through scripting patches. You can even edit internals if you really know what you're doing. The best part is the studio just uses the RavenDB API, so anything you see in there you know is possible to do yourself with a client library.
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