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.9 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
Features
MongoDB Atlas
Azure SQL Database
Database-as-a-Service
Comparison of Database-as-a-Service features of Product A and Product B
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
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
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 priced itself out of the market, so to speak. Nevertheless, we do have 2 or 3 large applications that are highly integrated in azure, and for those it's just too easy to use SQL Database instead of the on premise Oracle Database with VPN gateways etcetera.
We don't need a dedicated SQL dba because so many of the database maintenance operations are managed. A huge positive not only in budget but time constraints.
The ability to scale quickly is the biggest positive as our data needs change constantly.
Easy to migrate from legacy tools and systems, saving us on the need for redevelopment.