MongoDB Atlas for Government
MongoDB, IncReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
361 reviews
from
External reviews are not included in the AWS star rating for the product.
Friendly to use of collections
What do you like best about the product?
The mongodb GUI is very good to view the collection and manage to the databases
What do you dislike about the product?
The GUI of we cannot see the user details
What problems is the product solving and how is that benefiting you?
Easy to edit collections
Overpriced, Poor performance and some of the worse support I have ever had to deal with
What do you like best about the product?
I have nothing good to say about MongoDB Atlas.
What do you dislike about the product?
My story with Mongo began when I started a new software position, and they had a legacy version of their software product using Atlas.
Compared to our other infrastructure bills, Mongo was significantly higher for the amount of compute and storage we used ($3K per month). This is a managed service, so you would expect to pay a premium. Ok, sure, but then I expect great functionality, performance, and support.
The main problem began with Mongo when we needed to delete some data because they tie the CPU and memory tiers to storage size, so we were overpaying. Our application would run fine off an M10 dedicated cluster (the smallest tier), but it had automatically scaled to an M50 because of storage. This is already a bit disappointing because they are forcing customers to pay for more compute and memory than they need.
So we started deleting some data, but then we ran into problems. The data deletion process was really slow and also slowed our entire cluster down, causing lag and performance issues for our end users. But hang on, this makes no sense because we are paying for more CPU and RAM than we need, so why would we have this issue?
It took us three months to delete 500GB of data. In the meantime, our bill remained the same because you can't claim the space back without compacting the database. Ok, fine. So we ran compact(), but we only freed ~100GB on the secondary clusters.
Support gave us a script to run that can see how much storage can be freed.
In the end, we had to activate an expensive additional support plan costing us $500 USD per month to get support to run a re-sync command. This should have taken their support people 10 minutes, but instead, they mucked us around going back and forth on the ticket, taking three weeks to resolve.
A year later, we needed to delete some more data. We spent another five months deleting 800GB of data. Then we ran compact() and freed 300GB. Where is our other 500GB? We contacted some humans at Mongo, who really couldn't do much other than suggest we get funding to cover the $500 support for one month. Yes, we got the $500 credit, but when I went to reactivate support, it was going to charge us for three months for one month because Mongo retroactively bills you for three months when you reactivate. Wow, we started in a bad place, now I'm beyond frustrated; this is daylight robbery.
To this day, I am still fighting to reclaim some storage, but at this point, I'm going to recommend to our CEO that our dev team put some effort into moving away completely from Mongo.
I also need to mention that Mongo recommended we use their online archive features, but when we crunched the numbers, it was still quite expensive, and we would have to do significant work to make our application work between the regular clusters and online archive. So it was significantly more logical to just put the data in AWS S3, then delete it in Mongo.
If I can summarize my experience with Mongo, and I acknowledge mine is probably quite different to most, here it is:
Overpriced for the performance you get
Sneaky billing model where they tie CPU and memory to storage
Terrible and expensive support
Sneaky extra charges on reactivating support
Bad support escalation solutions - they couldn't just turn on free 'support'
Poor database performance
Slow delete operations
Ecosystem lock-in
Forced upgrades - no LTS releases
Let me sum it up this way: if your compact() command does not free up the space that is available on your cluster, then provide the customer with free support to do so.
I hate dealing with Mongo. Nothing is simple, everything is expensive, and the performance sucks.
If you are considering using Mongo, find something else. Even if you have to take a bit more time to learn AWS Dynamo, S3, or Aurora, you should do it; you will save time and money in the long run.
Mongo, you deserve this negative review. I have given you plenty of opportunities to resolve things and have escalated issues, but you just don't care.
We wanted to move away from Mongo before; now I can't get rid of it fast enough.
Compared to our other infrastructure bills, Mongo was significantly higher for the amount of compute and storage we used ($3K per month). This is a managed service, so you would expect to pay a premium. Ok, sure, but then I expect great functionality, performance, and support.
The main problem began with Mongo when we needed to delete some data because they tie the CPU and memory tiers to storage size, so we were overpaying. Our application would run fine off an M10 dedicated cluster (the smallest tier), but it had automatically scaled to an M50 because of storage. This is already a bit disappointing because they are forcing customers to pay for more compute and memory than they need.
So we started deleting some data, but then we ran into problems. The data deletion process was really slow and also slowed our entire cluster down, causing lag and performance issues for our end users. But hang on, this makes no sense because we are paying for more CPU and RAM than we need, so why would we have this issue?
It took us three months to delete 500GB of data. In the meantime, our bill remained the same because you can't claim the space back without compacting the database. Ok, fine. So we ran compact(), but we only freed ~100GB on the secondary clusters.
Support gave us a script to run that can see how much storage can be freed.
In the end, we had to activate an expensive additional support plan costing us $500 USD per month to get support to run a re-sync command. This should have taken their support people 10 minutes, but instead, they mucked us around going back and forth on the ticket, taking three weeks to resolve.
A year later, we needed to delete some more data. We spent another five months deleting 800GB of data. Then we ran compact() and freed 300GB. Where is our other 500GB? We contacted some humans at Mongo, who really couldn't do much other than suggest we get funding to cover the $500 support for one month. Yes, we got the $500 credit, but when I went to reactivate support, it was going to charge us for three months for one month because Mongo retroactively bills you for three months when you reactivate. Wow, we started in a bad place, now I'm beyond frustrated; this is daylight robbery.
To this day, I am still fighting to reclaim some storage, but at this point, I'm going to recommend to our CEO that our dev team put some effort into moving away completely from Mongo.
I also need to mention that Mongo recommended we use their online archive features, but when we crunched the numbers, it was still quite expensive, and we would have to do significant work to make our application work between the regular clusters and online archive. So it was significantly more logical to just put the data in AWS S3, then delete it in Mongo.
If I can summarize my experience with Mongo, and I acknowledge mine is probably quite different to most, here it is:
Overpriced for the performance you get
Sneaky billing model where they tie CPU and memory to storage
Terrible and expensive support
Sneaky extra charges on reactivating support
Bad support escalation solutions - they couldn't just turn on free 'support'
Poor database performance
Slow delete operations
Ecosystem lock-in
Forced upgrades - no LTS releases
Let me sum it up this way: if your compact() command does not free up the space that is available on your cluster, then provide the customer with free support to do so.
I hate dealing with Mongo. Nothing is simple, everything is expensive, and the performance sucks.
If you are considering using Mongo, find something else. Even if you have to take a bit more time to learn AWS Dynamo, S3, or Aurora, you should do it; you will save time and money in the long run.
Mongo, you deserve this negative review. I have given you plenty of opportunities to resolve things and have escalated issues, but you just don't care.
We wanted to move away from Mongo before; now I can't get rid of it fast enough.
What problems is the product solving and how is that benefiting you?
A simple managed database to get up and moving quickly as a developer.
MongoDB- Ease and portable
What do you like best about the product?
Portability, easy to fire up, and requires less resource
What do you dislike about the product?
So far nothing I have found that concerns me about mongo
What problems is the product solving and how is that benefiting you?
I use MongoDB to save embedding for my chat model
One of the best database platform
What do you like best about the product?
MongoDB's simplicity is amazing. You can store data how you like, amend it as per your preferences, and implement the changes as you want to.
What do you dislike about the product?
Only one thing, the collections are not updated automatically.
What problems is the product solving and how is that benefiting you?
It helps in making changes on the live projects. It helps in setting up our backends of our projects and we can fix the issues in the application on real time basis.
Using vector search feature for the products
What do you like best about the product?
It's scalability and incorporating latest trends in the product
What do you dislike about the product?
May be the cost. I think cost should be reduced
What problems is the product solving and how is that benefiting you?
We are hosting our product embedding/vectors in the vector index that is being used to find the most similar vectors quickly
Easy to use, flexible and secured.
What do you like best about the product?
It is NOSQL database which is easy to use and installation. It is secured and easily manageble. It is cost effective.
What do you dislike about the product?
The sources regarding this are very less according to other database. Althought it is easy to use but sometimes need some support.
What problems is the product solving and how is that benefiting you?
I used it for saving databases of CRM project of clients. With this I am able to access database remotely. And I can manage easily. With this database we can save unstructed data without any issue.
Great database, with some caveats
What do you like best about the product?
Fast, intuitive, great documentation, ease of use, ease of ramp up, many programming languages support out of the box, fast and reliable
What do you dislike about the product?
Vast documentation that is very hard to navigate and find the info you need, very expensive support plans
What problems is the product solving and how is that benefiting you?
We have numerous clusters and we no longer need to maintain them ourselves.
Great for small development teams and early projects. Flexibility is great for growing startups.
What do you like best about the product?
MongoDB Atlas makes it easy to scale and adapt a changing data source. There are also nice features included that improve the developer experience, like data sync and their GUI tool, Compass.
What do you dislike about the product?
Certain computationally complex querying, across data types can be much more difficult than in a relational/SQL database.
What problems is the product solving and how is that benefiting you?
Data storage and syncing - their device sync has made it easy to build realtime experiences for our users across client platforms (web, iOS, Android).
Database management with mongodb atlas
What do you like best about the product?
It provide very faster way to create project database.Here we can create clustures and connect database to our project.It provide device sync,data fedration and stream processing services.User can create collection and many more functionalities are there to make your project faster.
What do you dislike about the product?
I always use this for my projects and i dont have anything to dislike about it.
What problems is the product solving and how is that benefiting you?
Build better apps faster with App Services,it provide option for adding data,create charts,create schema and create clustures etc.
Great Userfriendly Data Base
What do you like best about the product?
the best part is the connection process and DB creating process
MongoDB Atlas can make a database within a few simple steps and has multiple connection methods available it can easily connect with Nodejs and compose and the security is also good can access multiple IP addresses is available and work with no sequal querys have inbuild mail alart there is so many good things are available for mongoDB wonderful data base
MongoDB Atlas can make a database within a few simple steps and has multiple connection methods available it can easily connect with Nodejs and compose and the security is also good can access multiple IP addresses is available and work with no sequal querys have inbuild mail alart there is so many good things are available for mongoDB wonderful data base
What do you dislike about the product?
im working with mongoose last 2 year still i dont have any notable negative pointes about mongoDB
What problems is the product solving and how is that benefiting you?
simple and efficient database that does need to creat a collection and Documents early it can creat new collections automatically and supports Nodejs, javascript, and other languages also it has no sequel language and has a lot of inbuilt queries are there in the major I am using this for MERN full stack developing application.
showing 1 - 10