IBM Cloud Databases are open source data stores for enterprise application development. Built on a Kubernetes foundation, they offer a database platform for serverless applications. They are designed to scale storage and compute resources seamlessly without being constrained by the limits of a single server. Natively integrated and available in the IBM Cloud console, these databases are now available through a consistent consumption, pricing, and interaction model. They aim to provide a cohesive…
N/A
MongoDB Atlas
Score 7.8 out of 10
N/A
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
Pricing
IBM Cloud Databases
MongoDB Atlas
Editions & Modules
No answers on this topic
Dedicated Clusters
$57
per month
Dedicated Multi-Reigon Clusters
$95
per month
Shared Clusters
Free
Offerings
Pricing Offerings
IBM Cloud Databases
MongoDB Atlas
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
IBM Cloud Databases
MongoDB Atlas
Considered Both Products
IBM Cloud Databases
Verified User
Anonymous
Chose IBM Cloud Databases
When launching the system, using multiple services would have been inefficient, so we consolidated it on IBM Cloud Databases. We regularly compared the services provided by IBM Cloud Databases' PaaS with those of other cloud services, but decided that there was no need to go to …
a powerful storm disrupted power supplies and network connections to the data center hosting our critical databases. Despite the external factors causing widespread service disruptions, IBM Cloud Databases demonstrated its exceptional reliability. The auto-failover feature …
UI is easier to use and flexible. AWS EBS is very simple to use and do upgrades and monitor the upgrades easily. I also recommend IBM to implement these.
The reason why I choose IBM Cloud Databases is that the IBM cloud toolset is already being used in other functions of the company and by using IBM Cloud Databases, the other cloud tools are better embedded and integrated. If the company is set to use amazon tools, I would go …
IBM cloud database has a lot of features than amazon dynamodb. This is my personal opinion. But I can't say amazon dynamodb is a bad one. But IBM cloud database has a lot of securities and file storage and backup features than amazon dynamodb. But both are good in their own …
I have used Amazon DynamoDm and compared to IBM Compose, I would say IBM Compose is affordable, easy to use and very fast as well. I would opt IBM Cloud Databases given the two choices
they do a great job at handling our business needs. we like what they offer and how they respond to questions we provide. they do a lot of great things that help our business thrive and stay ahead. we are grateful for how this compnay has responded to our unique requests and …
We already had existing contracts with IBM and Microsoft, so those made the most sense to verify. Both are good options for data storage. Since much of our existing Dbs are IBM related, we stuck with IBM cloud dbs, just so that the SQL code would port well. Additionally, we …
The kubernete service is the front end for the transactions of our core systems and our cloud databases (Postgres and DB2) are the persistence storage.
It is very similar to the way on which we operated before except that we don't have to worry about high availability, backups …
AWS RDS & Oracle OCI. AWS RDS has a wider range of databases but at a higher cost. IBM Compose has fewer databases but is perfect for data related solutions like data warehousing (IBM Db2 AI enabled Warehouse is a GREAT product!)
Cloudant is HIPAA compliant and replicated out of the box. We recommend use of Cloudant vs Mongodb for that purpose. We use Redis only as a session cache.
We have Cassandra database that is currently not available as part of IBM Cloud Databases. We ended up using classic infrastructure IaaS to host our Cassandra server.
I did compare IBM Compose for PostgreSQL with PostgreSQL offerings available from Amazon and Google. IBM Compose was judged easier to provision and maintain.
I'm pleased with the additional more granular provisioning flexibility and more favorable cost structure that has come …
While at the time, Amazon RDS did/does not create Mongo databases, I was able to set up many with PostgreSQL databases with the same ease as IBM Compose. However, IBM compose does seem to offer a more intuitive application control panel. Amazon RDS costs run on a server …
We selected Compose because we initially thought that they would provide great support, and that they would bring encryption at rest within months. That has not materialized yet.
We also thought that the cost, while far from being the lowest, was reasonable.
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 …
Less Appropriate Scenario: 1) Small Scale or Low Budget Projects 2) Organizations with limited expertise in cloud technologies may find the learning curve steep, especially if they are not familiar with the IBM Cloud platform 3) If database requirements are highly dynamic and change frequently, the comprehensive features and management provided by IBM Cloud Databases might be overkill. A more flexible, self-managed solution could be preferable for adapting to rapid changes.
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.
The ease of setup was effortless. For anyone with development experience, a few simple questions such as name and login data will get you set up.
The web application to manage cluster settings, billing settings and even introspect the data was simple and most importantly worked all the time. This can not always be said for web interfaces of other products.
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.
Better cost reports, before just increasing to another tier, thus increasing the price. This is critical for early stage startups, where budget is tight.
Add more data center options. As a comparison, a similar service, Aiven.io has dozen more options than Compose (basically all big cloud providers). We moved from AWS to Digital Ocean, which made us stop using Compose, since Compose forces us to be either on IBM or AWS.
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
IBM Cloud Databases' pricing structure is easy to understand, and if you choose the right product, you can operate your system at minimal cost. Although there is ample documentation available, there doesn't seem to be a user community running on it, so specific usage know-how and troubleshooting can sometimes take longer than expected.
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
Support is helpful enough, but we haven't always had questions answered in a satisfactory manner. At one time we realized that Compose had stopped taking database snapshots on its two-per-day schedule, and had in fact not taken one for many days. Support recognized the problem and it was fixed, but the lack of proactive checks and the inability to share exactly what happened has caused us to look elsewhere for production work loads
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
The reason why I choose IBM Cloud Databases is that the IBM cloud toolset is already being used in other functions of the company and by using IBM Cloud Databases, the other cloud tools are better embedded and integrated. If the company is set to use amazon tools, I would go for rds.
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