MongoDB Atlas for Government

What do you like best about the product?

Mongo DB is used in our migration work: we pull data from the Facebook API, load it into Mongo collections, and then move that Mongo data into BigQuery. The best part about Mongo is that we can handle most of the major transformations directly within the Mongo collections before loading it onward.

What do you dislike about the product?

The query part is quite tricky, and sometimes the Mongo server doesn’t work.

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

For us mongo is extracting the data from API's and further performing the transformation on various collections

What do you like best about the product?

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 the product?

less suitable for complex joins, memory consumption and data duplication

What problems is the product 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 the product?

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 the product?

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 queries

What problems is the product 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 the product?

It is how flexible the document-based structure is for handling real project data. I use it in Node.js backend projects where storing JSON-like data directly as documents makes development much faster compared to traditional relational databases. Adding new fields or updating schemas is simple, so I don’t have to redesign tables every time requirements change. The performance is also very good for read and write operations in smaller web applications and APIs. I’ve integrated it with Auth0 to manage user data after authentication and the workflow feels smooth. MongoDB Atlas onboarding was straightforward, and connecting databases to applications took only a few minutes. Overall, it helped me build and scale backend projects more quickly with less database management complexity.

What do you dislike about the product?

It is that managing complex relationships between data can become difficult compared to SQL databases. In one of my backend projects, handling deeply connected user and task data required extra queries and manual structuring. I also noticed that if indexes are not configured properly, query performance can slow down as the database grows. MongoDB Atlas is easy to start with, but pricing increases quickly when storage and usage scale up. Debugging aggregation pipelines can also become confusing for more advanced queries. Overall, it works great for flexible data structures but complex data handling and scaling need careful management.

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

It solved my problem of handling flexible and changing data structures in backend projects. Earlier, whenever project requirements changed, modifying tables and schemas in relational databases took extra effort and slowed development. With MongoDB, I can store JSON-like documents directly, which makes it much easier to manage user data, project details, and API responses. In one of my Node.js projects, I integrated it with Auth0 to store authenticated user profiles without creating complex database tables. Querying and updating data became much faster during development. It also reduced the time needed for database setup and schema changes.

What do you like best about the product?

I mostly use MongoDB Atlas as the cloud database for my web projects and small full-stack applications. I like how straightforward it is to create a cluster and connect it to my Node.js apps with Mongoose. It has helped a lot with deployment and day-to-day database management by giving me a consistent, reliable environment that I can access from anywhere.

I also appreciate not having to manage servers myself or handle backups manually. On top of that, the schema-less approach makes updates simpler than with more structured databases. I really value the flexibility of the document schema for unpredictable development needs, since it lets me reorganize data without dealing with traditional relational tables. Overall, the document model saves me a lot of development time because I can add new fields and adjust how information is stored without repeatedly restructuring the database.

What do you dislike about the product?

For personal project its great but when I have to implement a dedicated cluster for a client project the jump from M0 to M10 is quite large in terms of pricing. I also feel that whenever I am trying to run deep analytical query or try to join multiple tables together things get messy, it also can be very heavy on CPU cluster if my indexes aren't perfectly optimized.

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

I like how easy it is to implement. I don’t have to worry about installing MongoDB on a cloud server, configuring firewall rules, managing security updates, or dealing with anything complicated. I’ve been using this since I was a novice in development, and using Atlas has helped me a lot because I don’t have to think about major connection or configuration issues when I move a local database to production.

What do you like best about the product?

Reachable and always ready. Its easy to use. I dont need to make my own onpremise clusters anymore, i can use that time more productively with Atlas !

What do you dislike about the product?

Everything is ok. Free tier is little slow but okay fair enough.

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

mongo atlas really calm and peaceful place that helping people solves their big db confused moments because their platform is very friendly and easy to use. Also secure.

What do you like best about the product?

Going from a SQL background to NoSQL wasn’t easy at first, but it ended up paying off in a big way. I built our full ERP/eCommerce system using MongoDB, and it really accelerated development.

When I started this project 8 years ago, I was warned not to choose NoSQL because it supposedly wasn’t recommended for this type of project. I’m glad I didn’t follow that advice.

What do you dislike about the product?

It’s very fast overall. The only time I notice it slowing down is during lookups when there’s a lot of data. Even then, it’s super easy to create data indexes and optimize everything.

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

It transforms slow SQL DB design into an easy, auto-created document with a clear structure. It really helps speed up development.

What do you like best about the product?

Mongodb is fine-tuned , performance supporting Database, feature liks Integration, Pricing and ROI,Schema Flexibility,High Scalability,Rich Query , Language, AI features

What do you dislike about the product?

TTL Indexes :Automatically delete old documents after a time period. Useful for logs/sessions, but not very exciting.
Replica Set Elections :Internal process for choosing a primary node during failover. Important for reliability, but mostly infrastructure mechanics.
Write Concerns: Controls how safely data is written across replicas. Critical in production, but configuration-heavy.
Capped Collections :Fixed-size collections that overwrite old data. Niche use case.
BSON Size Limits :Technical limitation discussions (16 MB document limit) are practical but not fun.

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

It is solving scheme flexiblity and performance problem

What do you like best about the product?

I mostly use MongoDB Atlas for my cloud database in web projects and small full-stack applications. I enjoy how easy it is to create a cluster and integrate with my Node.js applications using Mongoose. MongoDB Atlas has helped me significantly with deployment and database management, providing a consistent and available environment from any location. I like that it allows me to stop managing the server and handling backups manually. The schema-less nature makes it simpler to handle updates compared to structured databases. I really enjoy the flexibility of the document schema, which caters to unpredictable needs in development, making it easier to reorganize the database without dealing with traditional relational tables. The flexible document model saves me a lot of development time by allowing me to easily add new fields and change how information is stored, without needing to restructure the database repeatedly.

What do you dislike about the product?

The dashboard can be a bit overwhelming if you don't have a working knowledge of cloud databases. There are areas such as clusters, metrics, networking configuration, backup, and security. I had to frequently refer to the documentation to understand which specific configuration was needed to change. The error messages did not give much away, so it ended up being more troubleshooting configuration than the backend.

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

I use MongoDB Atlas for cloud database management in web apps, simplifying deployment across environments and stopping server-side hassle. Its flexible schema handles frequent data updates easily, saving me development time and reducing effort compared to traditional databases.

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