Flexible document workflows have accelerated schema changes and simplified evolving data models
What is our primary use case?
In my day-to-day work, I use MongoDB Atlas primarily for storing and querying semi-structured or dynamic data where schema flexibility is important, as I work extensively on schema design, indexing, and query optimization. For example, in a system like policy or config management or aggregator response, the data structure evolves frequently and can be nested. MongoDB Atlas allows me to store data in document-oriented format and avoid complex joins, making faster reads possible.
A specific example in my project where MongoDB Atlas made my work easier and faster is that we store data as flexible documents, which allow us to onboard new partners or change the schema without requiring database migration or downtime. This made our development faster. We handle dynamic policy or config data for hotels, and the structure of the data varied across partners and kept evolving. Some had nested rules and different fields and optional attributes. MongoDB Atlas made our work easier to handle evolving nested structured data while maintaining performance and reducing development overhead.
One more aspect of my use case where MongoDB Atlas fits in our workflow is that I typically use MongoDB Atlas for flexible or read-heavy data, especially when the schema evolves frequently, and I combine it with Redis as a caching layer for hot data. This helps me balance flexibility and performance, and MongoDB Atlas acts as a primary store of semi-structured data while Redis handles low-latency accesses. Another important aspect is faster development cycles. Because of MongoDB Atlas's schema flexibility, I can iterate quickly without worrying about strict migration, which is very useful in fast-moving product environments. Since it is managed by MongoDB Atlas, I also benefit from high availability, automatic scaling, and monitoring, which reduce my operational overhead and allow me to focus more on building features.
What is most valuable?
One of the best features of MongoDB Atlas is that it provides a fully managed database. One of the biggest advantages I think is that MongoDB Atlas is a fully managed service, meaning it handles deployment, scaling, backup, patching, and maintenance automatically, which allows developers to focus more on application logic instead of infrastructure. Apart from this, there are a few more things I appreciate, such as easier scalability, higher availability, built-in monitoring and performance optimization, and security and compliance.
Among managed service, scalability, high availability, and built-in monitoring, one of the most valuable aspects for my team is that we focus more on the fully managed database service, which significantly reduces operational overhead. Instead of spending time on provisioning, scaling, backups, or handling failures, those responsibilities are handled by MongoDB Atlas. This allows engineers to focus more on building features, optimizing performance, and solving business problems. It also improves development speed and reliability. For example, setting up an environment or scaling during traffic spikes becomes much faster and safer without manual intervention.
MongoDb Atlas combines multiple capabilities into a single integrated platform. Features like automated backup, monitoring, scaling, and security all working together make it much easier to manage production systems compared to stitching together multiple tools. This improves not just operational but also developer confidence in the platform to handle many failure and scaling scenarios automatically.
What needs improvement?
MongoDB Atlas currently has almost all the features we require, but there are some points where I see certain improvements. One area is cost visibility and optimization. Since pricing is largely based on storage and cluster size, it can sometimes be difficult to predict or optimize cost without deeper insights. More granular cost breakdowns or recommendations would be helpful. Another area I can mention is performance tuning transparency. While MongoDB Atlas provides monitoring and suggestions, debugging deeper issues like slow queries, index efficiency, or shard imbalance can sometimes require more control or visibility. Cost optimization, deeper performance insight, and easier scaling decisions would make MongoDB Atlas even more powerful.
A couple of additional areas where MongoDB Atlas could improve are integrations and developer experience. For integrations, while MongoDB Atlas supports major cloud providers and tools, deeper and more seamless integration with observability patterns would make troubleshooting distributed systems easier. On the documentation side, while it is generally good, some advanced topics like sharding strategies, performance tuning, and real-world scaling patterns could benefit from more practical guidance. Additionally, a better local-to-cloud development experience, making it easier to replicate production-like MongoDB Atlas environments locally, would help developers test performance and scaling scenarios more efficiently.
For how long have I used the solution?
I have used MongoDB Atlas for a long time; to be specific, I have been using MongoDB for around two plus years of experience.
What do I think about the stability of the solution?
From my use case, I can easily say MongoDB Atlas is very stable, and it is used on a global level. It is stable, and since it is a managed service, features like replication, automatic failover, and backups are handled by the platform.
What do I think about the scalability of the solution?
MongoDB Atlas is highly scalable. One of its main features, because of which I use MongoDB Atlas, is its scalability. It supports both vertical scaling and horizontal scaling through sharding, where data is distributed across multiple nodes. This allows the system to handle large datasets and high throughput efficiently.
How are customer service and support?
Customer support for MongoDB Atlas is very good. I remember I had a case where I needed to reach out for customer support. Most of the issues I encountered, like query performance or indexing, were handled internally through monitoring, optimization, and best practices. MongoDB Atlas has strong documentation and a large community, which makes troubleshooting easier. For any infrastructure-level concerns, my platform team typically coordinates with the provider if needed.
Which solution did I use previously and why did I switch?
Before MongoDB Atlas, we were mostly relying on MySQL, where we did SQL queries. MySQL worked well for structured data and transactional use cases, but we started facing challenges when dealing with dynamic and nested data structures, especially where the schema kept evolving. Handling such changes required frequent schema migration and joins, which increased development effort and sometimes impacted performance. We moved to MongoDB Atlas for that specific use case because it provides schema flexibility and better support for document-based data.
How was the initial setup?
For pricing and setup cost, those are managed by my infrastructure or platform team, so from a developer perspective, I am not directly involved in these things. However, from a user perspective, I understand that costs are mainly driven by cluster size, storage, and throughput. Because of that, we remain mindful about efficient schema design, indexing, and avoiding unnecessary data growth. From a setup standpoint, MongoDB Atlas made it quite easier.
What was our ROI?
We have seen a return on investment; while we do not have the exact numbers, as it is saving our time and making our development easier, we can easily say the cost is being reduced. My team is using it even after a long time, and the main reason is that it provides cost savings.
Which other solutions did I evaluate?
Before choosing MongoDB Atlas, I explored a few options; one of them was using a relational database that includes JSON columns for flexibility. However, that still required managing schema constraints and did not scale up well for deeply nested or evolving data structures, especially with complex queries. I also considered other NoSQL solutions like DynamoDB, which offered good scalability, but it had more rigid access pattern design and less flexibility for ad-hoc queries and evolving schema compared to MongoDB Atlas. MongoDB Atlas stood out because it provided a good balance for schema flexibility, rich query capabilities, and managed infrastructure.
What other advice do I have?
For advice, I would want to give to others who are looking into using MongoDB Atlas is to design your data models because of access patterns rather than trying to replicate a relational schema. MongoDB Atlas works best by leveraging embedding for related data and avoiding unnecessary joins. It is also important to invest early in proper indexing because performance on MongoDB Atlas is heavily dependent on how well queries are supported by indexes. One more thing to tell others is to plan for scaling and sharded key selection upfront if you expect large data volumes since changing it later can be complex.
Overall, I want to say MongoDB Atlas is very powerful, but getting the best out of it requires thoughtful data modeling, indexing, and planning for scaling from the beginning. My review rating for MongoDB Atlas is 9 out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Ensures efficient team collaboration with quick deployment and easy integration
What is our primary use case?
We are using MongoDB Atlas for our log storage, transactional log storage, and we are into CPaaS business, communication platform as a service.
We are also using PostgresSQL in some of the applications, alongside MongoDB Atlas.
What is most valuable?
The most valuable features of MongoDB Atlas in handling large data volumes include collection size and its NoSQL database capabilities.
The security features of MongoDB Atlas support our organization very well.
My company has seen financial benefits from using MongoDB Atlas because we are using open source.
What needs improvement?
There is nothing about MongoDB Atlas I would like to improve or any weak points at this time.
I have not thought through what other features I would like to see included in future updates.
MongoDB Atlas should support containerization.
For how long have I used the solution?
I have been using this product for the past 5 years.
What was my experience with deployment of the solution?
I find the installation process easy to deploy as it wasn't difficult to implement.
What do I think about the stability of the solution?
The stability of the product is very high, and I would rate it a nine out of ten for stability.
What do I think about the scalability of the solution?
It's very much scalable, and I would rate scalability a nine.
How are customer service and support?
For premium support, I would rate the support of MongoDB Atlas a nine.
Premium support requires additional payment; otherwise, you can manage whatever you can yourself.
Though I am currently not using support, I would rate it a nine.
How would you rate customer service and support?
How was the initial setup?
I personally took part in the installation process.
I can deploy MongoDB Atlas in 2-3 hours.
What about the implementation team?
When we make changes, responsibilities are always distributed. It will be a team whenever a production deployment comes.
What was our ROI?
My company has seen financial benefits from using MongoDB Atlas through savings because we are using open source.
Which other solutions did I evaluate?
Postgres is another option that is available for us. I have considered alternatives for MongoDB Atlas.
What other advice do I have?
The database team consists of five to six people.
We are not currently using the AI functionality in MongoDB Atlas, though AI-driven projects are available in their vector search.
Based on my experience, I would recommend MongoDB Atlas to other users looking for NoSQL databases.
We do everything on our own and are not using third-party services for maintenance.
I am involved in the maintenance process.
We are using MongoDB Atlas for commercial purposes.
The number of people currently using this product in my organization is related to my platform hosted on MongoDB Atlas.
I think it's a competitive solution compared to others, though I cannot comment on pricing as I haven't seen pricing for other products.
I rate MongoDB Atlas a nine out of ten.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Room for improvement in data handling leads to enhanced cost-effective data management performance
What is our primary use case?
I primarily use Oracle databases, but I work with many other databases such as
MongoDB Atlas and several cloud databases. I utilize
MongoDB Atlas predominantly for training-level projects in resource grooming and for sub-projects at my office. It is used alongside Oracle and Postgres in these training layers.
What is most valuable?
MongoDB Atlas offers replication, which is cheaper than Oracle RAC, making it appealing to certain industries. It is particularly useful for unstructured and semi-structured data because of its performance in these areas. Sharding and partitioning are supported, though they don't reach the same level as Oracle's capabilities. This cost-effective solution assists organizations in data storage and management.
What needs improvement?
It would be beneficial if MongoDB Atlas could better support OLTP aspects and data frames, as well as enhance its capabilities for data pipelines and visualization dashboards. Furthermore, supporting the medallion architecture could be a valuable addition, and incorporating improved spatial and vector handling for geographical data could make it more competitive. Enhancing vector processing for AI capabilities would also be critical.
What do I think about the stability of the solution?
MongoDB Atlas is effective for unstructured and semi-structured data, but when it comes to OLTP transactions, its performance declines. This is a continuous challenge I face when utilizing MongoDB Atlas.
What do I think about the scalability of the solution?
MongoDB Atlas offers sharding as a scalability feature, although it does not perform as well as Oracle. Partitioning is also available; however, it lacks a multi-tenancy architecture, which affects its scalability in comparison.
How are customer service and support?
Technical support from MongoDB Atlas, which is open source, is satisfactory in most cases. However, when compared to top databases like EDB, Postgres, and Oracle, the features of MongoDB Atlas fall short, resulting in an average rating due to higher-expectation features still lacking in its offerings.
What's my experience with pricing, setup cost, and licensing?
The price of MongoDB Atlas is reasonable, which is why many organizations, including mine, are opting for it.
What other advice do I have?
The overall rating for MongoDB Atlas is around 5.5. To improve,
MongoDB should enhance support for demanding graph databases, vector databases, and spatial handling. Additionally, improvements in AI capabilities, particularly vector processing, are imperative. These developments could provide MongoDB Atlas with a competitive edge.
