MongoDB Atlas (pay-as-you-go)

What do you like best about the product?

Speed of iteration
flexibility
strict relational consistency

What do you dislike about the product?

no enforced schema
harder data governance

What problems is the product solving and how is that benefiting you?

problem- rigid schemas slow teams down
benefits- store flexible docs

What do you like best about the product?

What I like most about MongoDB is how much it speeds up real-world development without getting in the way.

From a daily workflow perspective, the document model is the biggest win. I store data in the same nested structure my APIs return, so I don’t spend time joining tables or reshaping responses. That alone cuts hours when building or modifying endpoints.

The aggregation pipeline is something I use regularly for dashboards and analytics. Instead of writing extra backend logic, I handle filtering, grouping, and transformations directly in the database, which keeps my codebase cleaner and faster.

On the UI/UX side, MongoDB Compass and Atlas make a difference. Being able to visually inspect documents, test queries, and manage indexes saves a lot of debugging time compared to purely CLI-based workflows.

Performance-wise, proper indexing (especially compound indexes) has significantly improved query speeds in my apps, often turning slow endpoints into near-instant responses.

An unexpected benefit has been how well it handles rapid product changes. I can ship features without locking into a strict schema early, which has made iteration much faster and reduced rework.

Overall, it’s improved my workflow by reducing boilerplate, simplifying data handling, and letting me move faster from idea to production.

What do you dislike about the product?

What I dislike about MongoDB mainly shows up as the project grows.

The biggest issue is schema inconsistency. Since validation isn’t strict by default, collections can end up with mixed document structures. This has caused bugs for me in production because different records don’t follow the same shape. I usually fix this with Mongoose or custom validation, but it adds extra complexity. Stronger, more opinionated schema enforcement out of the box would help.

Handling relationships is another weak spot. $lookup works, but it’s not as clean or performant as SQL joins for complex relations. In some cases, I’ve had to duplicate data or restructure things, which increases maintenance overhead. A more optimized and developer-friendly way to handle relations would improve this.

On the UI side, tools like Compass are useful, but they can feel slow or limited when working with large datasets. Querying and exploring big collections isn’t always smooth. Better performance and more advanced debugging tools would make a difference.

Pricing can also become a concern with MongoDB Atlas as usage scales. Costs increase quickly with storage and operations, which impacts ROI for smaller projects. More transparent cost optimization suggestions would help developers manage this better.

Overall, these issues don’t block usage, but they do add friction as the system scales.

What problems is the product solving and how is that benefiting you?

MongoDB mainly solves the problem of rigid data models slowing down development.

We struggled with frequent schema changes and migrations in relational databases, but now we can evolve document structures on the fly, which has resulted in much faster feature delivery.

We also struggled with complex joins and reshaping data for APIs, but now we can store related data together and fetch it in a single query, which has reduced backend complexity and improved response times.

In terms of impact:

Development time for new features reduced by ~30–40%
API response times improved (e.g., ~400ms → ~150ms in some endpoints)
Less time spent on migrations and schema refactoring

Overall, it’s made our workflow more flexible and significantly faster, especially in fast-changing products.

What do you like best about the product?

The flexible schema is the biggest advantage of MongoDB, and it also provides support for many data types. It scales well because it offers sharding. It also supports complex queries, aggregation pipelines, and multiple index types, which makes data retrieval both flexible and powerful.

What do you dislike about the product?

One drawback of MongoDB is that its flexible schema can result in data inconsistencies if it isn’t managed carefully. Also, compared with relational databases, it’s generally less well-suited for complex transactional systems. If we are building a system like a bank, or anywhere data consistency is most important, this can become a real concern.

What problems is the product solving and how is that benefiting you?

MongoDB addresses the challenge of working with unstructured and rapidly changing data by offering a flexible schema. For me, this speeds up development, makes it easier to adjust to new requirements, and simplifies the way data is stored and retrieved. On top of that, its support for sharding enables horizontal scalability, so applications can handle increasing data volumes and traffic more efficiently.

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.

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.

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.

I have used MongoDB Atlas for a long time; to be specific, I have been using MongoDB for around two plus years of experience.

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.

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.

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.

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.

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.

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.

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.

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.

Public Cloud

Amazon Web Services  (AWS )

What do you like best about the product?

Mongo DB is a no sql database so we need no fixed schema for storing data. Mongo DB is very easy to integrate into our project or web application. The setup was also very easy. It has good documentation also. I really like the user interface of both atlas and compass.

What do you dislike about the product?

Mongo DB doesnot have any strict schema and has little support to complex relationships it sometimes leads to hard data management.

What problems is the product solving and how is that benefiting you?

Mongo DB helps me to handle unstructured data. Mongo DB helps me for fast integration and development. We can simple scale our applications also.