RavenDB is a NoSQL Document Database that is fully transactional (ACID) across the database and throughout clusters. It is presented as an easy to use all-in-one database that minimizes the need for third party addons, tools, or support to boost developer productivity and get projects into production fast. Users can setup and secure a data cluster deploy in the cloud, on…
First of all, Microsoft Access is also a powerful, efficient, and free database. But the feel of it, I mean the GUI is not all great for me. It is very eye-stressing. MongoDB is also a good database, it too is efficient, productive, and powerful. But, upon this, RavenDB is a …
The team is very nice, very helpful, and answer very fast to any answer you may have. Thanks to their help, we were able to use and understand all the RavenDB features in no time! Documentation for server and client is very clear, with a lot of use cases. Maintenance is easy, …
RavenDB is just smarter than the competitors. The mapping reduction sorting is head and shoulders above everything else I've used. Nothing really approaches comparable in terms of complexity. Because of the searching of predetermined categories, read efficiency is terrible. …
Verified User
Engineer
Chose RavenDB
The company needed a cache server that was closest and the most accessible, which is why we are currently experimenting with RavenDB which gives us the option to set up our hub in a local setting.
Verified User
Team Lead
Chose RavenDB
Much better support, more transparent pricing, much more easy setup process, native integration into c# / net core. We also tried to set up a Mongo Atlas cluster by self-study but weren't able to get this running. There is a much better response when searching in google, but a …
While MongoDB is in general more popular, I cannot fathom why that is. If you want ACID support (and as a developer, you'll always want that), MongoDB is way slower when compared to RavenDB. Furthermore, RavenStudio is just integrated, while
Verified User
Director
Chose RavenDB
Flexibility and performance really set RavenDB apart.
[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 …
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 …
Installing and configuring. We had some big issues with indexing the data after the documents were created and wanted to expand the index, with millions of records this task mostly did not complete despite a dedicated server.
Out of the many variants of document and SQL databases out there that we have used, RavenDB is our no 1 choice for anything but the smallest projects which can be served with a very small SQL instance. Other than that, RavenDB packs more features and is easier to work with than …
Verified User
Consultant
Chose RavenDB
The given alternatives are also powerful and really good noSQL databases but the highest availability of RavenDB allows me/us to know it a lot better. RavenDB is encrypted by default wherever we use it in production and it has a high level of documents compression.
Verified User
Manager
Chose RavenDB
As I have said before in the previous questions ... RavenDB has a very simple clean UI, but stacks up in its power. Though new to me, I have found it to be much easier to learn and use than my previous database - Microsoft SQL Server. RavenDB's simple design and meaningful …
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.
When I first started using RavenDB, I did evaluate Mongo DB but found it to be lacking. The primary issue was that Mongo DB did not support atomic consistency for the persistence of multiple documents at the same time, although I think this may not be an issue with subsequent …
Once I had got my head around the concept of a document database it was a happy bye-bye to SQL Server. Firebird - far too fiddly - I found myself writing a silly API to sit on top of Firebird just to do the most basic things. MongoDB - in the very short time I spent with it, it …
We chose Raven over Mongo because it has robust support for multi-document transactions, first-class .NET and LINQ support, a well-designed API that has inspired imitation and has better tooling out of the box. We chose Raven over Redis because Raven is a full persistent …