MongoDB Atlas is the company's automated managed cloud service, supplying automated deployment, provisioning and patching, and other features supporting database monitoring and optimization.
$57
per month
Azure SQL Database
Score 8.3 out of 10
N/A
Azure SQL Database is Microsoft's relational database as a service (DBaaS).
$0.50
Per Hour
Pricing
MongoDB Atlas
Azure SQL Database
Editions & Modules
Dedicated Clusters
$57
per month
Dedicated Multi-Reigon Clusters
$95
per month
Shared Clusters
Free
2 vCORE
$0.5044
Per Hour
6 vCORE
$1.5131
Per Hour
10 vCORE
$2.52
Per Hour
Offerings
Pricing Offerings
MongoDB Atlas
Azure SQL Database
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
MongoDB Atlas
Azure SQL Database
Considered Both Products
MongoDB Atlas
Verified User
Anonymous
Chose MongoDB Atlas
In general, they all compete against each other, and each solution has its own advantages and disadvantages. While MongoDB Atlas was the way to go for some cases, however, other databases were more fit for some services that MongoDB Atlas, especially if they were managed by us, …
MongoDB Atlas has been in the market for very long time and there are bunch of documentation, training and support for it. It also is specifically designed for the use case similar to our project and big companies in the market uses them for very high load which made us …
Both AWS RDS and MongoDB Atlas provide a state-of-the-art managed database hosting service, with the difference being the type of databases they support. AWS RDS does not support MongoDB engine and Atlas only supports MongoDB. So I consider them complimentary services and we …
MongoDB Atlas has an excellent rating out there in the market. They have a great supporting team as well. When we have questions about technical stuff, they respond fast. The performance of MongoDB Atlas is the key factor that we choose to use. Because it has such an easy way …
Vice President, Chief Architect, Development Manager and Software Engineer
Chose MongoDB Atlas
MongoDB is a great product but on premise deployments can be slow. So we turned to Atlas. We also looked at Redis Labs and we use Redis as our side cache for app servers. But we love using MongoDB Atlas for cloud deployments, especially for prototyping because we can get …
When choosing a NoSQL, open source database, MongoDB is the clear winner from an implementation standpoint. For databases that are better suited for highly-organized data, a traditional database engine like MySQL, PostgreSQL, or Oracle's RDBMS may be a better choice. When the …
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 …
I would recommend MongoDB Atlas to every company who have a significant need in the NoSQL database and do not want to manage their infrastructure. Using MongoDB Atlas can significantly reduce your management time and cost, which saves valuable resources for other tasks. It also suits a smaller company as MongoDB Atlas scales up and down very quickly.
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.
Generous free and trial plan for evaluation or test purposes.
New versions of MongoDB are able to be deployed with Atlas as soon as they're released—deploying recent versions to other services can be difficult or risky.
As the key supporters of the open source MongoDB project, the service runs in a highly optimized and performant manner, making it much easier than having to do the work internally.
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.
For someone new, it could be challenging using MongoDB Atlas. Some official video tutorials could help a lot
Pricing calculation is sometimes misleading and unpredictable, maybe better variables could be used to provide better insights about the cost
Since it is a managed service, we have limited control over the instances and some issues we faced we couldn't;'t know about without reaching out to the support and got fixed from their end. So more control over the instance might help
The way of managing users and access is somehow confusing. Maybe it could be placed somewhere easy to access
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.
I would give it 8. Good stuff: 1. Easy to use in terms of creating cluster, integrating with Databases, setting up backups and high availability instance, using the monitors they provide to check cluster status, managing users at company level, configure multiple replicas and cross region databases. Things hard to use: 1. roles and permissions at DB level. 2. Calculate expected costs
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.
We love MongoDB support and have great relationship with them. When we decided to go with MongoDB Atlas, they sent a team of 5 to our company to discuss the process of setting up a Mongo cluster and walked us through. when we have questions, we create a ticket and they will respond very quickly
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.
In general, they all compete against each other, and each solution has its own advantages and disadvantages. While MongoDB Atlas was the way to go for some cases, however, other databases were more fit for some services that MongoDB Atlas, especially if they were managed by us, which means less cost, like Redis for example
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.