MongoDB Reviews

What do you like best about MongoDB Atlas?The most useful thing I’ve found is actually a very basic feature, but it has genuinely saved me. When I was performing a migration in a client environment at my company, I had to constantly keep track of which database/connection I was currently working in. MongoDB Atlas lets you color-code connections, so I can immediately tell, “Okay, I’m in this DB/this connection,” without second-guessing myself.What do you dislike about MongoDB Atlas?Recommendations to others considering MongoDB Atlas?Another thing I like about MongoDB Atlas is how easy it is to use with Node.js, Python, Golang, and other languages. They also provide automatic monitoring, so I can see things like CPU usage, and there’s autoscaling in place. That means I don’t have to worry as much about whether I’m handling the right number of users or if the setup is sized properly.What problems is MongoDB Atlas solving and how is that benefiting you?

What do you like best about MongoDB Atlas?I like the speed of response that MongoDB Atlas offers. The clients need faster response to interact with chats, and MongoDB Atlas works well in this aspect. Switching from Postgres to MongoDB Atlas also simplified the process of database maintenance for me.What do you dislike about MongoDB Atlas?I find that MongoDB Atlas could use more integration with Rust, which is a bit of a limitation for my needs. Additionally, having more documentation available and resolving current problems with Rust integrations would significantly improve my experience with the platform.What problems is MongoDB Atlas solving and how is that benefiting you?MongoDB Atlas simplifies maintaining databases and delivers faster responses for client interactions in chat applications.

What do you like best about MongoDB Atlas?Performance Advisor provides helpful insights into query performance. The index usage information also offers a clear view of how our application code is using indexes, which makes it easier to understand and improve overall performance.What do you dislike about MongoDB Atlas?DISK IOPS is not clear because it depends on various backend infrastructure. I have experience with AWS ENI, and in my case it wasn’t obvious how the DISK IOPS would behave or what to expect.What problems is MongoDB Atlas solving and how is that benefiting you?I manage a large Mongo cluster with around 40 TB of data. Performing maintenance used to be a hard task. If I needed to increase disk space, I had to expand the disk and rebalance RAID across my volumes in EC2. That has been resolved after migrating to Atlas. I enabled auto-scaling for storage, and I also enabled online archives.

What do you like best about MongoDB Atlas?MCP integration. Multi-Tenant Architecture. Ability to seamlessly increase the size of the cluster. The Performance Advisor is also a great feature.What do you dislike about MongoDB Atlas?Sharding doesn’t feel very intuitive to me. I have to stick to a single shard to prevent elements from reappearing.What problems is MongoDB Atlas solving and how is that benefiting you?Scaling, reliability, and implementation.

What do you like best about MongoDB Atlas?.Easy configuration, flexibility on upgrades, available on AWS and GCPWhat do you dislike about MongoDB Atlas?Price and the capacity for free trial planWhat problems is MongoDB Atlas solving and how is that benefiting you?I don’t know

What do you like best about MongoDB Atlas?I use MongoDB Atlas to store data for my startup, and I find that being a cloud-based solution makes it very easy to scale and operationalize. It's flexible and agile as a SaaS product, and I can turn it on and off quite easily. I'm overall satisfied with the experience because there's a lot that they offer, even more than I'm currently using. I also started afresh with MongoDB Atlas, and it was quite easy to start with, especially with the free plan, which shows how powerful the product is. It makes me want to upgrade to enable more features. Moreover, it was beneficial knowing a colleague had used it before, which reassured me, and I found the initial setup very easy.What do you dislike about MongoDB Atlas?N/AWhat problems is MongoDB Atlas solving and how is that benefiting you?MongoDB Atlas is a cloud-based solution that's easy to scale and operationalize. It's versatile, allowing us to start small and easily upgrade to access more features, making it a flexible and agile NoSQL database for our startup.

What do you like best about MongoDB Atlas?MongoDB Atlas made it easy to get a fully managed database up and running for a personal project without worrying about server maintenance or manual setup, which mattered since this was a side project with no dedicated infrastructure budget. Storing expense and balance records as flexible documents fit naturally with how the roommate bill-splitting data was structured, without needing to design a rigid relational schema upfront. The free tier covered everything needed for a small user base, making the ROI excellent, and the setup process combined with clear documentation meant I was productive within a short time without needing any paid support.What do you dislike about MongoDB Atlas?Since it's a managed cloud service, there's less control over fine-tuning performance at the infrastructure level compared to self-hosting, though this wasn't a real issue at the small scale of this project. Some of the more advanced querying and aggregation features have a learning curve if you're used to relational databases and SQL syntax. There's also no built-in AI-assisted query optimization, so understanding indexing and performance tuning relied on manual research rather than any smart guidance from the platform itself.What problems is MongoDB Atlas solving and how is that benefiting you?MongoDB Atlas removed the need to manage database infrastructure myself for a small personal project, letting me focus on building the actual bill-splitting logic instead of server maintenance. Storing flexible expense records without a strict schema made it simple to adapt the data structure as the project's needs evolved, and the free tier meant I could run this reliably without any hosting cost for a project shared casually among a few roommates.

What do you like best about MongoDB Atlas?I like MongoDB for its data-based storage and schema flexibility. It allows me to store data in non-table formats and handle any kind of data, unlike SQL databases where I had to stick with a predefined schema. The horizontal scaling feature and the easy learning curve also make MongoDB valuable to me. The initial setup of MongoDB was very easy for my team.What do you dislike about MongoDB Atlas?less suitable for complex joins, memory consumption and data duplicationWhat problems is MongoDB Atlas solving and how is that benefiting you?I use MongoDB to store data in a non-table format, accommodating any type of data. It offers schema flexibility and the ability to store data in key-value pairs, unlike SQL's rigid tables. This change helps with horizontal scaling and provides an easy learning curve.

What do you like best about MongoDB Atlas?The UI is easy to navigate, with a well-defined sidebar and admin settings that are simple to access. Overall, it just makes sense.What do you dislike about MongoDB Atlas?There's no mongosh terminal. You can't run aggregations easily and you can just forget about multi-collection joins. I understand that Atlas is like the admin control hub for MongoDB and complex queries and joins are supposed to be run using Compass but the web UI should offer an easy segue into using mongosh or if not, then atleast a panel to run complex queriesWhat problems is MongoDB Atlas solving and how is that benefiting you?Atlas is a great admin control command center. It makes it easy to set up access, manage users, and configure IP whitelists.

What do you like best about MongoDB Atlas?Best about MongoDB is its flexible document schema that lets me store JSON-like data without rigid table structures, perfect for my data analyst work. MongoDB delivers sub-100ms real-time data retrieval speeds, making it incredibly fast for querying and analyzing large datasets. The horizontal scaling through sharding lets me easily handle growing data volumes without performance drops, which is essential for event data management systems. MongoDB's native JSON/BSON document model means I can work with data in the same format I use in my code, eliminating conversion headaches and boosting developer productivity. Rich ad-hoc queries, powerful indexing, and built-in aggregation pipelines let me perform complex real-time analytics and data transformations directly in the databaseWhat do you dislike about MongoDB Atlas?One thing I dislike about MongoDB is that it doesn't support multi-document ACID transactions as robustly as traditional SQL databases, which can be problematic for applications requiring strong consistency across multiple operations. MongoDB's memory usage can be quite high since it relies heavily on RAM for caching and performance, requiring more infrastructure resources compared to some other databases. The lack of native joins means I often have to handle data relationships in application code rather than at the database level, which adds complexity to queries and can impact performance. Additionally, data duplication is common in MongoDB due to its denormalized document model, leading to increased storage requirements and potential data consistency challenges when updating duplicated fields across multiple documents.What problems is MongoDB Atlas solving and how is that benefiting you?MongoDB solves the problem of rigid, fixed schemas in traditional databases by providing a flexible document model that lets me store evolving data structures without complex migrations, speeding up my development significantly. It solves scalability challenges through horizontal sharding, allowing me to handle massive volumes of meter data and event records without performance degradation, which is crucial for my MDMS work. MongoDB's high availability through replica sets ensures zero downtime for my applications, automatically failing over to secondary nodes if the primary fails. The database solves the impedance mismatch problem between code and data by storing JSON/BSON documents that match my application's data structures, eliminating conversion overhead and boosting my productivity as a developer.