TrustRadius Insights for RavenDB are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Excellent Performance: Many users have consistently praised RavenDB for its excellent and optimized performance. They have been impressed with the high level of performance that RavenDB delivers, especially when considering its rare system requirements. Users find that RavenDB consistently meets their expectations for efficient and reliable database operations.
User-Friendly Interface: Reviewers have found RavenDB to have a highly user-friendly interface. The intuitive design makes it easy for users to navigate through the platform and perform various tasks. The visually appealing UI adds to the overall positive experience of using RavenDB, making it a popular choice among users who value simplicity and ease-of-use.
Efficient Configuration: Several users appreciate that configuring RavenDB is a seamless process thanks to its support for C# code integration. This feature allows developers to easily integrate automated tests into their workflow, streamlining the development process. In addition, reviewers specifically highlight how well RavenDB integrates with .NET Core and C#, further enhancing its efficiency as a NoSQL database solution.
We build software, back and front, and in my case, I need a small DB for a serverless app that needs to be fast, reliable, and flexible.
Pros
fast connection and data serving
making data readable and understable
Cons
I think the docs could be improved, and guides added for some main use case (like integration for SPA, serverless, etc.)
I believe the studio interface could be simplified
Likelihood to Recommend
While the learning curve can be kind of steep for people less familiar with general database knowledge, it is a great tool that seems to be customizable for pretty much any need one may have.
It is a great product, especially can be told as a powerful database, very efficient and easy to use. It is not a SQL-based database. My experience while using it was user-friendly and speed works. It helped our team to hold a huge amount of data, which we could do in other software databases. I have used this product, and it's very easy to understand. It is very productive and while I used it, I didn't find any mistakes in it. Well working product.
Pros
Storage capacity
Efficiency
Speed work
Cons
Tools
Lags a bit
Better GUI
Likelihood to Recommend
In simple words, I would say then if we want to store a bunch of important data, we would think for having a data manager, and a data manager would think for having a nice, efficient, and powerful database, and the one will always try to use, something which is very productive and professional. These qualities are present in RavenDB. We have not found anything very wrong with this product, very well performed. I know the work efficiency found in this product. No one can find anything not in order. Perfect build, just I think that the GUI could be better. Else, great product.
We were looking for a database solution for our clients, able to: manage huge databases (millions of elements by tables); offer a very fast response time (less than a few milliseconds); offer efficient mass database operations; secure and backup easily all the data we have; able to manage real-time operations; your data your server: on-site database solution;
Pros
secured by design
really fast database response time
awesome team support
Cons
license cost by cpu
Likelihood to Recommend
We use RavenDB for critical database projects for clients, where we need fast response time in huge database operations, with fewer downtimes as possible. For example, migrating one project that was started on the firebase database. We've reduced by 40 times the cost of infrastructure, and improved by 10x the database response time!
Our company was searching for an efficient caching solution that can also serve as a storage hub for company data and decided a few years ago to experiment with RavenDB. Employees are free to store data at will and use the available technologies for web development purposes. It has been primarily used for cache stacking and session-sharing and thus far has been receiving good reviews among workers.
Pros
Easy to learn and fully utilize. The tools made available are very simple and system maintenance is largely hands-free
Quick memory caching
Free of major errors. Any data is immediately stored to the hub
Can dual as a channel for stream data
Cons
Would like to see RavenDB develop a self-monitoring tool for bottlenecks
Needs a bigger community around the software. Difficult to find an immediate solution when faced with a new problem
Creating and configuring uncommon settings can sometimes be difficult
Likelihood to Recommend
RavenDB would be an excellent option for any projects requiring cache. It has the capacity to take on a big volume of input at once without any performance issues. If the solutions you are searching for are related to cache or key operations, RavenDB would provide good results.
VU
Verified User
Engineer in Information Technology (Computer Software company, 201-500 employees)
For me, RavenDB is the best database currently available.
RavenDB is a document database written in C# / .NET (Core) which is also the technology we use for our backends. It is super easy to configure a RavenDB server / database from C# code. This gives extra compile-time safety compared to other DBMS that use script languages like e.g. SQL. Furthermore, being a document database, I do not have to deal with the Impedance Mismatch that comes with any RDBMS. The entities that I store and load from RavenDB more closely resemble the code that I would actually write as an O-O developer. Nonetheless, I have ACID support in RavenDB, something that is not quite as well implemented in e.g. MongoDB.
RavenDB can be easily integrated in automated tests with their RavenDB.TestDriver package. This makes integration tests on CI pipelines especially easy as we do not have to supply e.g. a Docker image that provides a corresponding database server instance.
With RavenDB, the RavenStudio comes directly as a web frontend with the server. I do not need to install tools like SQL Server Management Studio or SQL Developer to get quick (scripting) access to my RavenDB databases. Furthermore, the free edition of RavenDB has less constraints than competitive projects (e.g. unlimited database size) and even if we need to buy a paid license, the prices are way more acceptable than from other big vendors.
All in all, RavenDB allows us to deliver software faster for our customers by making our data access layers easier to design, implement, and test.
Pros
Document Database - no Object-Relational Impedance Mismatch
ACID support that is optimized for performance
Can be easily integrated into automated tests (unit tests)
Easily configurable via C# code
Comes directly with RavenStudio - no SSMS or SQL Developer required
In general low footprint when it comes to memory and disk consumption
Useful safety nets for new developers - e.g. by default an exception is thrown when you make too many requests within a session
Cons
Configuring the JSON Serializer was a little bit hard in one project
Creating custom indexes from several documents can sometimes be a bit cumbersome
Likelihood to Recommend
RavenDB is our default OLTP database for new projects - there have to be specific requirements from our customers to not use it. It is a very versatile tool that we can incorporate in many situations.
Granted, we haven't used RavenDB in projects where we have several hundreds of millions or even billions of documents. However, we never had any issues with the performance so far (and we have databases that gather about a few GBs of data in a few months). It might be that RavenDB is also not the best thing for modeling a data warehouse (OLAP) as it is relatively cumbersome to create custom indexes.
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.
Likelihood to Recommend
RavenDB works well in any situation where you'd normally use an OLAP database. It works well as a caching server or key/value store as well. You are able to store whole documents and load them on demand with all the data your aggregate root needs to display. This makes developing with it much easier, too, since you are able to store an object graph instead of breaking everything up into some level of normalization that your database likes. This still allows you to query across documents if needed using custom indexes.
If you need an OLAP database for reports, a traditional SQL database is probably a better fit.
We had a performance struggle to store millions of records including history per day into a relational database. The time series included in RavenDB solved this problem for us. Currently, all the users have their own database and history, now we need to make to switch to a shared history and partially shared database.
Pros
JSON Format
Features offered like time series and revisions
Lucene Search
Attachments on Documents
Cons
Documentation REST endpoints
Best Practices in most common situations
Likelihood to Recommend
I think it is suited in almost all scenarios. We have implemented it in eCommerce solutions and other SaaS solutions
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.
Pros
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
Cons
High on-premise prices.
Not a vast community.
Likelihood to Recommend
It's suited to all kinds of projects unless it's reporting related, for which you should use ETL of RavenDB as well.
I use RavenDB for all my projects that require data persistence. Document Store databases solve the problem of programming model/persistence model impedance. RavenDB has an amazing feature set that sets it apart from its competitors. The power and speed provided by its dynamic indexing makes writing complex and performant queries simple. And the focus on security and resiliency inspires tons of confidence. I have used RavenDB since v1 and with every release, it just keeps getting better!
Pros
The C# client makes using RavenDB feel like a natural part of the C# language.
Support is top notch! Even using free support you get speedy replies from engineers responsible for development of the DB engine.
The hosted cloud product is reasonably priced and makes it easy to deploy a resilient cluster with automatic backups.
Cons
I have never encountered any tasks that RavenDB could not handle.
Likelihood to Recommend
I suppose that if your data is flat and your schema is static, a Relational DB might be better suited.
We use RavenDB throughout our platform, from high-frequency server statistics to customer data. Our platform is challenged by the unique requirements of a geographically distributed regions, low tolerance for latency and the need for ACID state machines and transactional operations.
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.
Likelihood to Recommend
Extremely likely. The solution itself is very easy to setup, supports multiple languages out of the box and provides an easy-to-use administration UI which accelerates development. I have also actively used RavenDB in multiple other projects to a notable increase in productivity and a reduction in the burden of managing application data. The community license is very generous and allowed us to get started quickly without upfront costs and the support was above par.