RavenDB is a NoSQL Document Database that is fully transactional (ACID) across the database and throughout clusters. The database 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-premise or in a hybrid environment. RavenDB offers a Database as a Service solution, allowing users to pass on all…
N/A
Azure SQL Database
Score 8.3 out of 10
N/A
Azure SQL Database is Microsoft's relational database as a service (DBaaS).
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. …
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.
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
[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 …
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.
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 …
Better and more useful automation tools are available. Better at scaling and hosting your data. Greater security around access of data and encrypting where required. Allows for seamless integration in other Azure solutions which allows for greater flexibility when using the …
Depending on the use case they stack up very well. Google and AWS are well suited multi-cloud strategies or those that need a high level of RDS performance.
Mainly response time. Azure SQL Database is very fast and very reliable when it comes to executing queries and gathering the data results. Also, the exporting options it gives are far exceeding expectations and enable users to accommodate any deliverable in a timely and …
I selected Azure SQL because it integrates nicely with the technology stacks we currently maintain. The pricing is right, and clients are happy with that. Scaling is easy. Most of our clients don't want to maintain a full-blown database server, and they don't need one. For …
The simplicity and great features and good support of Microsoft as well as the more reasonable flexible price than other competitors is one of the important reasons for choosing it.
Oracle database is "the" serious database. There really is no competition in that field. SQL Database would be a serious competitor through the ease of implementation and the "no maintenance," but since it's too expensive for "normal" use (medium to small applications), it just …
It is very easy to setup SQL database on Azure. one can always refer to their documentation for best practices. It is highly available and scalable. It is cheaper than its alternatives and provide better performance than others. As we are using many other services of Azure for …
Director, eCommerce Analytics and Digital Marketing
Chose Azure SQL Database
The Azure SQL Database, compared to our on premise SQL server installation, is much easier to use in terms of seeing database diagnostics. There is a whole visualization platform that comes with the tool that will allow your database administrator to see what jobs are tying up …
Amazon's RDS offering is actually very good and is used in other parts of the company, we just have a lot of Azure experience so wanted to leverage that.
Being able to manage our databases in the cloud, scale quickly, and only require access to VMs made choosing Azure a no-brainer over a traditional SQL Server installation/integration. We don't have the budget or resources to integrate and maintain servers on our own, so using …
I would say MySQL in either Aurora or MariaDB form come close however, Azure SQL Database has a more streamlined approach to delivering a consistent programmability model, supported drivers and feature set.
Azure SQL Database T-SQL is advantageous and more complete than SQL …
Azure owned by Microsoft who owned SQL Server, so provided a variety of tools for easy migration/transition and from on-premises to the cloud; and management. I recommend using Azure for any on-prem SQL server databases.
Azure SQL is a clear upgrade to SQL Server 2012 and pretty much has the advantage with all the extra features that it has. Security, queries, exporting tables, T-SQL has all improved. Transitioning 18+ years of an in-house database to the cloud was a struggle, but for the …
We moved away from Oracle and NoSQL because we had been so reliant on them for the last 25 years, the pricing was too much and we were looking for a way to cut the cord. Snowflake is just too up in the air, feels like it is soon to be just another line item to add to your Azure …
Amazon Relational Database Service is the other obvious competitor. We were already in Azure, so it's not a serious contender for our business due to that bias already, but I do personally find the marketing and documentation of RDS more intimidating to sort through.
Comparing with Amazon Aurora: Azure SQL DB is 100% compatible with SQL Server and Aurora is compatible with MySQL and PostGreSQL. Because of if, SQL DB suits large enterprises with hundreds of databases better. Comparing with Oracle: the main issue is that Oracle will try to …
It stacks up in different ways, for the most part, I think Microsoft is doing a really good job versus the competition. They basically started database type products from the beginning. I've always been excited about updates and can see their progress over time. Get's me really …
RavenDB is very well suited for NoSQL beginners to start easily setting up and using a NoSQL database. Also to set up a high performance and high availability cluster is possible without reading tons of documentation. Very straightforward assistant! The performance is really high.
Your upcoming app can be built faster on a fully managed SQL database and can be moved into Azure with a few to no application code changes. Flexible and responsive server less computing and Hyperscale storage can cope with your changing requirements and one of the main benefits is the reduction in costs, which is noticeable.
Scalability is #1: if it used to be an almost no-win endeavour to try to modernize your server or migrate to other hardware, with Azure SQL Database it becomes a press of a button.
All the tools simply work after you are on Azure SQL Database.
The applications do not need changes in order to start using Azure SQL Database.
Hybrid Cloud scenarios will work.
Clustering and failover - already there.
You can start monitoring the use and extract performance insights in a new way in Azure.
A little slow on processing complex or large Views. We use a lot of Views to feed our BI system, and the processing time could see some improvement, IMHO.
Additional monitoring components would be nice too, automating some built in performance measurement tools would be a nice feature.
Price can always be improved as well. It’s not bad, but room for improvement.
We've had an excellent experience using RavenDB. Internally we are testing the newer features in 5.0 such as time series, which will effect the con specified previously dependent on the real world performance. We foresee that BattleCrate will continue to use RavenDB as we grow.
Really good .NET client that is very easy to use. The management studio is excellent and puts anything that Microsoft or Oracle have to shame. Very quick to develop with once the complexity hurdle has been overcome. Initially using it can be a bit painful until you fully grasp the event sourced nature of the indexing.
The interfaces are intuitive once you are familiar with all the functions. The ability to use different tools to interact with the platform, such as directly via a browser or code editors such as VS Code or Visual Studio is a great option and allows for integrating withn the project and other testing and developing tools.
Had a question that was answered in minutes. Never used a NoSQL approach before, but was able to be proficient in a matter of hours. Easy to read API Documentation. 5 out 5 support in book, I have never once ran into an issue that wasn't quickly solved by either their support team or myself doing a quick search online.
We give the support a high rating simply because every time we've had issues or questions, representatives were in contact with us quickly. Without fail, our issues/questions were handled in a timely matter. That kind of response is integral when client data integrity and availability is in question. There is also a wealth of documentation for resolving issues on your own.
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. RavenDB is a storage system designed for the current websites and functional prototypes. It has an easy-to-use interface and enables quick replication and backup installation. Furthermore, technical assistance responds quickly and walks you through the implementation and deployment procedures.
I selected Azure SQL because it integrates nicely with the technology stacks we currently maintain. The pricing is right, and clients are happy with that. Scaling is easy. Most of our clients don't want to maintain a full-blown database server, and they don't need one. For them, Azure SQL is the right size.
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.