MongoDB Atlas Reviews

We use it for patient data.

Our databases used to be in-house. Now, they are in the cloud with MongoDB and everything is much easier.

The speed of it is the most valuable feature.

I would like a better dashboard. It could be made a bit more user friendly. 

We put a large amount of stress on it, and it is able to handle this all the time.

It is very scalable. We have 10,000 employees.

We receive great customer service.

Our purchasing experience on the AWS Marketplace was great. We chose to go through the AWS Marketplace as a small team; my team selected it, and we consist of three people.

The pricing and licensing is great.

We also looked at Cassandra, but we did not find it easy to use.

This product was selected because it was easier to use and more user-friendly.

I would recommend MongoDB.

The integration and configuration of the product on the AWS environment is fine.

We use the AWS version of this product.

We also use WebEx, and it works well.

For MongoDB as a service, there are two distinct ways to use it: as a personal user, where one can register on Atlas and experiment with its features; and as a professional, where one can use it for backup management, environment management, and creating figures. Additionally, MongoDB Atlas has features such as data lake capability, the ability to create charts from queries without using other BI tools, and Apache Lucene for text search. I have experimented with these features, but I have not used them professionally. The most relevant use for me is managing backups. Atlas MongoDB also allows for making REST calls and creating applications with triggers, although I have not used it for programming applications much.

It has a good easy to use gui and the ability to do most of the management operations under automation

The most useful feature is the management of the backup. I use a managed tool offered by MongoDB to manage an on-prem environment and compare it with the SaaS service and software. The solution is very ready-to-use and it is much simpler to manage backups, which cuts down on the amount of work and stress. However, at least two other features should be mentioned in the current versions. Search integrated with Lucene and the possibility of storing vector data. 

There are some Mongo new features that could be useful for the customers I work with, which are related to migration from on-prem to the cloud. MongoDB is currently working on these features. With the latest version of Mongo, there are new tools that help with migrating. However, currently, only Mongo can use these new features. Soon these migration tools should be released to the public and could really assist with migration also from SQL on-prem environment to Atlas.

I have been using the solution for four years.

The solution is very stable.

I give the scalability a nine out of ten. MongoDB is very easy to scale and with Atlas, it is possible with a few clicks and configurations.

The technical support team is skilled, prepared, and really helpful.

Positive

The initial setup is straightforward. Only one person is required for deployment.

For me, MongoDB Atlas could be expensive as every cloud service because I don't have many other terms of comparison, but I think it is not so expensive for customers. In the end, they may be able to save money rather than buy it on-premise however, on-premise, they do not have access to all the features that Atlas exposes. The costs are similar to having a cloud provider and if we look at the short-term, there is a real saving of money investing in their service instead of making it on-prem in the same scenario.

I give the solution an eight out of ten. I am not familiar with other SQL databases on the cloud. I know that Atlas is quite stable and the service is good, providing customers with all the necessary features to use it as a service. MongoDB Atlas is integrated and available on Google, AWS, and Azure.

I advise people to take advantage of the free courses from MongoDB University that are very well done to gain a general knowledge of MongoDB. Therefore, if someone has no experience with Mongo, they can get great preparation for the MongoDB University course without spending any money.

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.

The application we are working on is built on MongoDB.

MongoDB is a NoSQL tool. We can easily add fields. It provides more flexibility to store data. It is flexible to changes. I have not encountered any performance issues.

Searching and browsing through the collection must be made easier.

I have been using the solution for two years.

The product has been stable so far.

The installation was easy. The deployment took an hour. One person is enough to deploy the tool. It does not require much maintenance.

I am using the free version of the solution.

I have used DynamoDB before. MongoDB’s free version is quite good for our use cases. DynamoDB is expensive.

MongoDB is a very good tool for first-time users. Overall, I rate the solution an eight out of ten.

I use the solution for Web Application creation.

The solution is easily scalable and manageable. Tools can be easily added to the solution.

Customer support needs improvement knowledge-wise.

I have been using the solution for two years.

It is a stable solution. I rate the stability a ten out of ten.

It is a scalable solution. I rate it ten out of ten.

I rate the support an eight out of ten.

The initial setup is straightforward. The deployment takes three hours. I rate the initial setup a ten out of ten.

I have seen a 10% return on investment.

The solution is fairly priced. I rate the pricing a seven out of ten. 

I rate the overall solution an eight out of ten.

We store a lot of raw data in MongoDB and all our relational data is in RDS Aurora. We are still evaluating Aurora, however, primarily, most raw data is in MariaDB.

The solution is easy. It's just not the solution for every use case, however, it's very nice if you don't have structured data or you don't really worry about the structure all the time.

The integration capabilities are fine.

The dashboards are good.

The product is user-friendly.

The solution can scale. 

We don't have any issues with the solution at this time. It does what we need it to do. 

If it could be cheaper, that would make us happy.

I've used the solution for over five years. 

We don't have any problems with it. There are no bugs or glitches. It doesn't crash and freeze. 

The solution is scalable. If a company needs to expand it, it can do so.

We are a processing engine for financial transactions, therefore, we don't have a lot of users per se, however, we've got a lot of customers out there that use the functionality, the payment functionality that uses the system. While we don't have a user frontend all the time interacting with our database, it's basically systems talking to your database.

We've never had to deal with technical support yet, therefore, I can't speak to how helpful or responsive they might be.

Currently, I'm using Spring Boot on top of it and that's all I'm really worried about.

The initial setup is very simple and straightforward. It's not overly complex or difficult. You just create the database from the user's perspective, it's as easy as that. With AWS, it's not an issue anymore in terms of implementation. 

We have quite a big team of over 100 people and we're able to handle deployment and maintenance. 

We have a DevOps team that was able to handle the installation. 

You do get what you pay for. The solution isn't overly expensive. 

We don't have any subscriptions that I know of. We are paying for document DB, which is a clone of MongoDB. That's part of our whole solution.

Before choosing this solution we did not evaluate other options. 

I'd rate the solution at a nine out of ten. It's brilliant for what we are using it for.

I'd recommend the solution to others.

MongoDB can be used for many things. It's a document store, so you can add whatever collection you need to it. We use it for an application that we've built.

My team is not using it at this time, although other teams in the company may be.

The cloud-based nature of this solution makes it flexible and scalable. I like the fact that you can make the deployment bigger, as needed.

Not having to maintain it yourself is good.

Querying a dataset is not very intuitive, so I think that it can be improved.

I have been using MongoDB Atlas for approximately two years, although I am not using it for my current project.

This is a stable product and we plan to continue using it.

This is a very scalable product. There are approximately five users.

I have not had experience with technical support.

Prior to this solution, we have used PostgreSQL, which is a database. As a document store, MongoDB is fine.

You don't have to maintain it yourself.

We pay for licensing on a monthly basis and we are fine with the cost.

I would rate this solution an eight out of ten.

Our use case for MongoDB Atlas is not an as an RDBMS. It is a NoSQL database which means that it's not like a traditional database such as Oracle or Microsoft SQL Server. It's a NoSQL database, and it is much easier to manage. The scalability is very high, the performance is very high, and the cost is lower as compared to the traditional database for cloud.

The features that I have found most valuable include the very easy integrations. The integrations are fantastic. I have not faced any challenges from the integration standpoint.

In terms of storage, it is pay as you go storage so I'm just paying for the service.

The dashboards are very good, you can customize as per your requirement.

The configuration is so easy. It's very handy and user-friendly. You just need to open the portal page, configure your application, and you are done. 10 minutes are required, that's it.

In terms of what could be improved, I don't think we are in a position to give any kind of recommendation to the MongoDB service provider, because we still are in the evaluation phase. We are not mature. We just have six months of experience, and we have not found any challenges with that service provider where we could recommend that they need to add XYZ for this catalog.

I have been using MongoDB Atlas for the last six months.

We are using the latest version because it's always available since MongoDB is a cloud-based solution.

In terms of stability, stable means that you get the services from the cloud provider. MongoDB Atlas is a cloud service provider, and the stability, availability, and the whole thing is their responsibility. Nothing is connected with you. I'm just paying them to be triple nine availability, five times nine availability, depending on the kind of different plans we have. We take a plan with the cloud service provider and it is their responsibility that the database and services are up and running as per our requirement. We don't manage the database. We just use the database.

In terms of scalability, when you ask for the database, there is no direct user connected to the database. Let's suppose we are going on any kind of e-commerce site, for example you log into amazon.com to procure something. There are millions of users who are connected to the interface. But no one will be able to directly connect with the database. It's not like the users are going to directly connect with the database and see the optimization performance. It is a front end UI which will connect with the database itself.

Any product selection is based on the project's needs. We select the tools and technologies based on the kind of requirements we receive from the customer. So, today we are using MongoDB. Tomorrow we may use another DB, and the day after tomorrow we may use some other Postgres DB. We are not limited with one OEM supplier. We select our solution based on the customer's needs.

As you know, all cloud service providers offer different plans for support. It is up to us to select what plan we need from them. For example, there are entry level plans, mid-level plans, premium plans, golden plans, etc...

If I need to manage something, if I have any problem, and I want a MongoDB consultant to help me online to fix my problem, so I should opt to have a premium plan. Whenever we are stuck with some problem, we raise a ticket to the cloud service provider and we explain to them the problem we are facing. They analyze the problem and they help us in terms of suggestions and recommendation for how they would repair all those things. As far as the support goes, it's good.

The kind of support plan category you opt for from the cloud service provider is only design KPI and actually they provide the support. For example, if I choose the silver level entry plan, then the SLA will be from when I put my question inquiry until they answer it in 24 hours.

You need to understand, that's why I have recently opted for the silver plan. If I opted for the platinum plan, I will be able to get the answer within five minutes of the moment I log my ticket. That is called the platinum service. If I pay as a platinum service, I will get the response in five minutes. But if I get a service with a 24-hour response, that means I understood that I'm okay getting it then because I cannot pay or invest so much money on the support side.

My product selection is based on the customer's requirements. Every project has its own requirements. It's not that I don't like Oracle or the Microsoft SQL Server. But when I choose the database, it's based on the customer's needs only.

It's a software as a service, so you don't do any kind of installation. You just add the services in your application and you are good to go. You just need to buy an account, that's it.

You don't know where this database is being deployed and you don't know where the storage is. When we are working on the cloud, we don't know where exactly the service provider is storing the data. The only agreement we have with the service provider is for the security, the reliability, and the availability of our data, and that's it. But whatever is inside the data, that is our responsibility.

If you understand cloud computing, there is nothing called licensing. They call it a service - we are getting software as a service. We are not getting any licenses for that. If you need a service today, you use that service today, and if you don't require it tomorrow, you will discontinue with it. So you will not incur any costs from the licensing side. You will just pay as you go, that's it.

I would recommend MongoDB Atlas to be used by other people, because this is the current technology which everyone should use.

I am still new with it, but since I mentioned that I'm using this product for only the last six months and my experience with this product is good thus far, on a scale of one to ten, I would give MongoDB Atlas a six.