MongoDB Atlas Reviews

We use it in a cloud setup on Google Cloud Platform as part of a microservices-based cloud solution. These microservices communicate with messages, and one use case for MongoDB is storing specific messages we're interested in.

MongoDB has supported our organization's need for scalable and flexible data storage.

We use it internally, where different teams manage different microservices. Sometimes, internal incidents arise, requiring teams to dedicate personnel to resolve and communicate with other teams. 

With MongoDB, other teams can now access some of our data and investigate issues on their own, freeing up personnel for other tasks.

Moreover, this solution simplifies real-time data analytics or application development for our business.

It simplifies things by automating previously manual tasks. It acts as a self-service portal for our team, reducing manual work and enabling automation.

We're happy with the performance, maintenance, and especially the ease of use within Google Cloud.

Given our microservices architecture, it's like a large puzzle, and MongoDB feels like it fills the gaps we were facing. So, the global clusters feature has enhanced our application performance and user experience.

It helps us optimize team performance, which is valuable.

The initial configuration could be a bit easier.

I have been using this solution for a couple of years. 

We've experienced some issues, but most MongoDB issues are resolved quickly. The issues we face are mainly with other systems.

So, it is a stable solution. 

It is a scalable solution because we use quite a lot of data, and it handles it well.

It's a microservice solution, so each microservice runs on several pods, maybe eight. Each pod uses MongoDB and makes its own connections, so multiply by eight, maybe 100, so roughly a thousand users.

These are internal users, so we're fine with the current number.

MongoDB offers free support online, and they seem to be doing a good job overall.

We have used other databases as well, including Google Cloud, for the past two years on our current project. My company policy guides such decisions. Overall, the company is happy with MongoDB.

The setup is automated through our partner using Terraform for provisioning, not just for MongoDB but for our whole infrastructure. We manage daily deployments using TerraForm, and MongoDB setup on Google Cloud is very smooth.

The deployment is very quick. For example, microservices using MongoDB start very quickly, possibly within a minute.

We haven't had major issues with deployment or configuration. Maybe initial configuration fine-tuning for performance can be time-consuming, but the initial effort pays off later with reduced maintenance needs. 

Expertise in automation and deployment processes is helpful and worth learning within the team.

We do it in-house. It's integrated with Google Cloud, GitHub, and GitLab actions. Everything is cloud-based and easy to work with. It's been continually improving over the years.

We don't use external consultants, as we have in-house expertise. It's a 100% cloud solution.

We don't have engineers dedicated to maintenance. It's part of our continuous integration and delivery environment, so there's not much manual intervention needed. Issues usually arise when deploying incorrectly and rolling back, but deployment itself is straightforward.

In some teams, companies, and projects, there might be two to three people dedicated to everything, which is a lot. If these skills to analyze productivity or cost saving can be automated, these people can teach others and do more valuable work. It's all win-win.

The price is cheap enough. It is comparable and has average pricing. We have a long-term license.

The pricing is acceptable for enterprise tier.

We haven't faced any major issues so I would rate this solution a nine out of ten.

In this project, it's more integrated than previous ones. The level of integration, automation, and evolution is impressive when used well. It's flawless, straightforward, and hassle-free.

MongoDB Atlas is a schema-less database.

MongoDB Atlas is very easy to use and user-friendly, and you get what you're paying for. MongoDB Atlas is very easy to use when you are familiar with MongoDB and how to write query functions. I would give the solution a nine out of ten for usability.

MongoDB Atlas should improve its user experience by providing better explanations or a wizard for people working with its UI. The solution should include a query builder that will help people who aren't developers get data.

I have been using MongoDB Atlas for two years.

MongoDB Atlas is a stable solution.

MongoDB Atlas is a scalable solution. Around ten people were working with the solution in my organization.

The solution's initial setup is straightforward.

MongoDB Atlas provides good value for money. MongoDB Atlas is not expensive, and since it's a cloud-based solution, you pay by usage.

MongoDB Atlas is a cloud-based solution. The solution's installation, setting up, and integration are relatively easy. MongoDB Atlas provides the functionalities it promises.

Users should focus on the technical design and figure out how they want the data, what data scheme they're aiming for, how to build properly, and how to design data properly. For everything else, they provide you with enough tools to understand what you're doing pretty much by yourself.

Overall, I rate MongoDB Atlas a nine out of ten.

We primarily utilize MongoDB Atlas for tasks such as IoT integration. Additionally, it serves as a general-purpose database that aggregates analytics data before transferring it to a data lake. Its versatility allows for various applications, providing flexibility and ensuring the availability of essential data across different systems. While it is used in diverse contexts, many use it for IoT-related initiatives.

We prefer MongoDB Atlas over SQL because most of the data generated with IoT devices is unstructured. This gives you flexibility; you don't have to define specific schemas all the time, and sometimes, the structure of the object varies.

It improves data management along the same lines. MongoDB Atlas supports structured data with IoT projects.

MongoDB Atlas was explicitly designed to support IoT applications. Many databases offer features tailored for IoT use cases.

One area for enhancement is containerization. They could explore ways to facilitate deploying MongoDB containers within the platform.

I have been using MongoDB Atlas for five years.

I rate the solution’s stability a nine out of ten.

Two people use this solution because they work with sensors and other variations of IoT.
I rate the solution’s scalability a nine out of ten.

The tool provides a forum where users can engage with experts. These experts offer assistance tailored to your specific needs, whether you're focused on product-centric queries or diving deep into particular use cases. Ultimately, the support you receive depends on your requirements and the extent of your experience with the platform.

The initial setup of MongoDB Atlas is straightforward. The user-friendly UI guides you through the setup process seamlessly. It would be beneficial if they could maintain this simplicity across different operating systems. Additionally, if they can streamline the process to easily deploy with containers, it would greatly enhance user experience and make life easier.

MongoDB Atlas offers various options based on your needs. It can accommodate both, whether you require the enterprise version with advanced features or prefer to start with an open trial version.

Security is primarily organized around organizational principles, allowing you to customize and adjust each tool according to your specific security policies. I recommend the product. Every product serves a purpose as long as it addresses the right problem. MongoDB Atlas has proven particularly effective for applications such as analytics and IoT, making it a recommended choice for those use cases.

Overall, I rate the solution a nine out of ten.

There are many scenarios that MongoDB can fit into, like where there is a fluid schema and no transaction management.

This solution is deployed on a cloud and AWS is the provider.

It's flexible. We don't need to have a solid upstream availability failover, and everything is seamless in Atlas. They do all the replication, and all that is probably happening behind the scenes. The pricing isn't that high compared to any of the IBM products.

The biggest challenge we all have is an application layer level. One node is sitting in the APAC region, another node is sitting in the US and UK region. The seamless replication has to be lightning fast, but we haven't tested the scalability yet.

There's no straight answer for any of the database providers in that particular space. We don't have a failover, but when it comes to the RPA recovery point objective and RTO, we have to test it.

Atlas should think about a provision in the form of a commitment. You can ask for a longer commitment. Database is one thing. Once I build an application, if it goes to production, it's going to be there for the next 10 years minimum. In that way, somebody's giving you a commitment for five years, so you can give them a huge discount. If somebody's giving a two year commitment, you can give them a better discount. 

I've been using this solution for about six months. 

It's stable.

I haven't used this solution long enough to gauge the scalability. 

We haven't had any issues so far.

It's straightforward and seamless. Setting up takes about 35 minutes, but it could be as little as 20 minutes. We never had a concern with installation. Maybe when you're doing a data migration, that could be a different story altogether.

In development, we have about 15 users. The number of users could go up to 100,000 people because it's an application that we're building. We're building the system for 100,000 concurrent users.

We have the possibility of growing every year on year, probably 30%. We are going to test it to see if we can host multiple tenants in this single DB and if it will be scalable.

We pay for the license on a monthly basis. It's not cheap or expensive. For smaller companies, it's definitely expensive.

I would rate this solution 8 out of 10.

I would recommend this solution to those who want to start using it.

We store all our data in MongoDB. Our frontend application is .NET, our backend is .NET, and the database is MongoDB.

We have two products running on MongoDB: a financial expense management solution and a sustainability product.

It can store data as a flat file, similar to a file system. It's called Atlas GridFS and it works very well.

MongoDB is a very good database. The Community Edition is free, which is cost-effective for development.

The API support is excellent for integration.

From an improvement standpoint, MongoDB can improve security.

There are some challenges from a security point of view. Since the file can be easily accessed, there should be more security features. The data should be encrypted in some form to prevent unauthorized access.

We've been using MongoDB for three to four years.

I would rate the stability a nine out of ten.

We haven't seen high volumes of data yet. Our solution is for expense management, not a full ERP solution. So far, the system has been stable with the current number of users.

It should be scalable and easily work with other databases like SQL or Oracle. We shouldn't have trouble converting the data.

I would rate the scalability a nine out of ten. Some security features are still under development.

MongoDB isn't for our internal users; it's for our customers. Depending on the organization, it can go up to ten thousand or even a hundred thousand users. We have a lot of customers using our applications built on MongoDB.

We are a young company, only five years old. We recently started this product, but we know that around a hundred people are using it in one of our products for web and mobile.

We have a very strong internal technical team that manages everything. We haven't needed any support from MongoDB because our team is proficient in using it.

My team only recommended MongoDB. We haven't worked with other databases for our current projects. I have worked with SQL Server and Oracle in the past as an SAP consultant, but those were for ERP systems, not application development.

MongoDB's setup is very easy. We plan to only use MongoDB for our future database needs.

It works very well with the .NET and Angular platforms due to the flat file support. So, we went with that option.

The main benefits include cost savings and speed. The application runs fast, and accessing data is quick.

ROI is very good. 

It's very easy to manage for our technical data analysts.

Overall, I would rate the solution a nine out of ten. I recommend using MongoDB because it's free for development, scalable, and user-friendly for connecting with frontend and backend technologies like Angular and .NET.

We may use it as an application database. The application stores the data as documents in the database, which is a preference for our company because it’s a Document DB and a NoSQL database, which are preferred over traditional relational databases.

MongoDB has wrapped up the whole development lifecycle. MongoDB has multiple built-in tools such as MongoDB Shell, Compass, and other tools. It helps the developers to use that specific tool efficiently. Users do not have to worry about finding the tools and then installing and using that specific tool to communicate with their database cluster. MongoDB has a built-in option using MongoDB Shell or Compass for that purpose.

So, it has positively impacted the development speed and productivity.

There are many valuable features, but scalability stands out. It can scale across zones. You can define multiple nodes. They have also partnered with AWS, offering great service with multiple features, including built-in backup, all under the same roof, without the need for external tools.

So, the scalability feature supported our data growth overall. The growth of the database depends on the application side. The database aids in scaling when the application requires more storage. 

It’s configured to scale automatically across zones and regions, ensuring that performance doesn’t degrade even when scaling down.

The scalability aspect is quite difficult to implement. It should be much easier for the end user. You cannot use less than two nodes; you have to use at least two nodes, and they categorize their nodes, like m5, m10, and m20, according to their resource practices, which are also a bit expensive.

The end-user has to learn a bit about it. MongoDB has great content on its site. They call it MongoDB University. They actually have great content for that. Anyone can learn it, but one has to study it before diving into it or starting to use it.

I have been using MongoDB Atlas for almost three years.

The scalability is good. In my team, almost the whole development team is using it. So, there are around five end users. 

I contacted customer service and support for multiple purposes while configuring. The support is quite efficient, and the guidance is quite good. Initially, when I was working on it, I had to communicate with the support team.

So, I had a good experience with the support. 

Positive

The initial setup is not too difficult but can be somewhat tricky. 

It is tricky mainly in terms of configuration, especially if it's not internet-accessible, configuring it to stay within the same data center while allowing developers access without network barriers.

It is worth my money at the end of the day.

The pricing is not that expensive, but it can be, especially when we have deployed it across multiple zones.

If you want to go with NoSQL, I would suggest using MongoDB. 

If you are saving documents and prefer AWS services, AWS also has their DynamoDB for that purpose. I would suggest using AWS service if all of your services are already on AWS.

Overall, I would rate it a seven out of ten.

We restore our golden data from various sources and then push it to MongoDB. We make our CDP from MongoDB, which serves as a device-centric system.

There is a built-in feature called Autoscaling In MongoDB Atlas. This feature automatically adjusts the configuration of MongoDB based on the volume of users we ingest daily. Autoscaling dynamically scales the resources to accommodate the load when our data flow increases.

The real-time data visible within MongoDB Atlas is not accurate. If they can improve the UI that monitors real-time data. It's more impressive and more attractive. It could be more user-friendly.

I have been using MongoDB Atlas for two years.

The product is pretty stable.

The solution is scalable. Autoscaling supports it.

50 users are using this solution

Whenever we have doubts during configuration, we reach out for assistance. We must upgrade certain parameters in our MongoDB setup, prompting us to contact their support team. They resolve such issues within four to five hours.

The initial setup is not very complex. It is easy to use. It's easy to deploy on MongoDB. We push from GitHub. From there, we specify where the data is restored in MongoDB. We continue to connect. It puts the data and delivers it to Argo City.

The product has a yearly subscription.

We have assigned DevOps for security.

The overview and monitoring part will address this issue, and then we will use it to observe any increasing traffic on our website. We also monitor the rising number of connections due to this traffic. It's quite easy to oversee everything in one place. However, the UI isn't particularly user-friendly.

I've also used it in my previous company and found it handy and easy to configure, including easy capabilities.

We are establishing SLAs that are directly tied to MongoDB. All are interconnected with MongoDB. If MongoDB experiences downtime or RAM or CPU usage spikes significantly, users may encounter difficulties logging in. This reliance on MongoDB can pose challenges for user accessibility, particularly when considering the conferencing tools we use.

Overall, I rate the solution an eight out of ten.

We use it to power a software-as-a-service cloud solution to book meeting rooms, parking spaces, and workspaces. We have multiple clients using this solution. A Node.js backend is also being used along with Mongoose, and it is running on Cloud Run. Then there is a VPC connection to MongoDB Atlas.

The most valuable feature is that it's all web-based. So one can browse collections just from the web. MongoDB Atlas is easily accessible, quick to understand, and quick to learn. People who have never used CLI can hop into the web interface and browse the database.

When I edit a document from the web-based Explorer, a lot of clicking is involved, like changing data type manually from a drop-down. It would be super nice if I could just edit the document in a JSON format. The JSON-based document editor should have a multi-language feature. Also, it would be great if there was a connector for Google Looker Studio.

I have been using it for three years.

The interface could be more reliable. It is not a stable product because sometimes we see the explorer being down or unable to log data and the interface turning to the five hundred server error. However, it's ninety-five percent stable. I don't always trust it, but most of the time, I do.

It scales well. I can only hope that it would be possible to configure and that it could scale down quicker. Now it takes twenty-four hours to scale down.

We have 15 developers who regularly use the solution.

The experience with the first-level support was a bit annoying as they took a lot of hours to figure out the issue, even though it was clear what needed to be corrected. But the professional support team on the paid support plan gave a clear and detailed response.

Positive

We've used SQL in the past. While building our product, and our architecture, MongoDB was very simple and a better choice. We chose to switch to MongoDB Atlas specifically because we did not want to manage our deployment database on our own. We chose to use MongoDB Atlas because it was the best choice in the market for managing MongoDB databases. It has a proper interface, and it's easy to get started. Its ability to run on Google Cloud Platform is one of the key sectors as the rest of our efforts run on it.

The initial setup was super easy. It took 15 minutes to setup.

I advise others to use the solution. I would tell others to use the serverless option, but not for people near Frankfurt, as the serverless interface is unavailable for Google Cloud in Frankfurt.

I would give it an eight out of ten as it's easy to use and quick to start.