The administration is not very interactive. Most of the time, you don't need to interact with the database, just create a user and indexes. It's not very friendly for developers.

Based on its own habitat, it's not ACID compliant. If it had an ACID compliant option, it would be more useful for database administration.

One improvement that I would like to see is a feature to export changes made in the environment, such as creating a new user. MongoDB Atlas should provide a way to export this action programmatically, so that we can easily integrate it with our IAC tools and deploy it afterwards.

There is room for improvement in the cost of certain features like encryption. The web console isn't very intuitive, especially for large data. The new feature, Cube, for BI needs better documentation, and more workshops or videos would be helpful for users and developers. Additionally, real-time performance monitoring in MongoDB Atlas needs improvement.

I believe MongoDB Atlas has room for improvement in terms of providing more convenient UIs for data manipulation. At present, we are required to create an HTTP proxy after the database and then use the UI to communicate with the database via that proxy. If MongoDB Atlas could offer UI features to create tables and add or update records from them, it would eliminate the need for UI development. For instance, if we have a table or collection of orders and products, and MongoDB has charts, then MongoDB Atlas could offer some tables to create tables, create orders, create products, update orders, update products, and link orders and products. So, we are basically expecting a UI to change the database.

For the additional features, I think giving the UI or the user interface to create tables or something similar would help simplify creating orders and products for a layman with zero technical knowledge.

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.

The price of the solution should be reduced.

We need improved query performance. The query performance of MongoDB Atlas can be slow, particularly when working with large datasets. Improvements in query performance could enhance the overall user experience.

We would like integration with more third-party tools and services and more integration options with third-party tools and services to enhance their workflows. The most specific areas for improvement and additional features that would be most valuable will depend on the needs and use cases of the organizations using MongoDB Atlas

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.

We had some edge cases where auto-scale caused an issue where a node went offline at the same time and we had to deal with that. We had to reach out to support to resolve the issue.

There's a barrier entry in the support pricing from a sales point of view for a setup for a large number of small clusters so we had to fall back from purchasing the enterprise support for it.

The setup of integrations with cloud service providers as private connectivity and encryption can be improved.

It would be better if there were more integration capabilities with other products.

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.

In the past, MongoDB offered more features for free, but now it's quite limited. The free version is limited, and you need to pay extra to fully utilize it.

The pricing could be improved.

MongoDB Atlas should add more APIs in their Terraform module because sometimes I find it difficult to find the resources in their Terraform model.

A few areas that we have noticed as being problematic with the MongoDB Atlas include user access to the platform. Currently, it is difficult to restrict and control what actions a user can perform within the solution, which poses a challenge from an internal auditing perspective.

An area for improvement in MongoDB Atlas is that it does not support individual or personal database backup, though it supports cloud cluster backup.

I want a query feature added to MongoDB Atlas, or if it's available, improve on it. My team needs manual coding for the pipelines, for example, creating and executing pipelines. If the query feature of MongoDB Atlas has some improvement, then the process for pipeline creation and execution would be better.

The product's file storage documentation needs improvement.

The product should introduce database mapping between SQL queries and document queries.

The product does not have ORM.

The initial configuration could be a bit easier.

MongoDB Atlas would be better if it had facilities for data warehousing, data lake, or ETL jobs. It probably has this functionality for large data sets, but I've not read about it, and I'm not so sure.

It would also be great if it were easier to integrate MongoDB Atlas with AWS services. Native integration between MongoDB Atlas and AWS services would make the solution better.

In the next release of the solution, the company wants to receive better support from the MongoDB Atlas team.

The product's data aggregation feature needs to work faster.

I would like the solution to offer more integration capabilities since it is an area where the solution lacks.

The tool's implementation should be made easier.

The speed when combining two documents is concerning. In SQL, there are Joins. You can define relationships between two tables and go for complicated structures, but you can't do that for MongoDB Atlas. You can have logical structures that do the same thing, but they are really slow compared to the Joins in SQL. Combining two separate documents within a database is not recommended because it affects performance. So if they can make it faster and more efficient, it would be amazing.

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.

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. 

The import and export process needs improvement, i.e., getting in and out. Moving data from other databases into MongoDB, along with indexing, was challenging. However, it has been improving.

I would like them to make the product easier to use.

Customer support needs improvement knowledge-wise.

I would like to have better performance for user experience with the solution.

We had some bad trainers when we first came onboard and would rate them fairly low. They did not seem staffed properly to fulfill the training services that they offered.

I would like a more comprehensive dashboard. The UI can be difficult to understand.

Going forward, we would like to have pure AWS Cloud (native) storage instead regular storage on the AWS integration side.

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

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.

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

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.

The cost needs improvement.

During the configuration, we did some migrations where we had to reindex about 70,000 indexes, which took around an hour. They should improve this and optimize the indexing.

The UI application for MongoDB crashes a lot, so we would have to use a third-party plugin to make it work. It may have been improved by now.

The cost needs improvement. The product is good, but the cost that we paid for it is expensive, so it wasn't that valuable.

Masterless architecture for linear scale.