Offers reliable engine for legacy needs but requires enhanced cost management and AI features
What is our primary use case?
I am not a partner of MongoDB; I am just a customer.
I do not use MongoDB in AI projects; only CosmoDB is used for AI projects, as MongoDB is an old pattern for us, and the new workload in AI is for a new pattern, which is CosmoDB for AI apps.
I would recommend MongoDB because it is a good pattern and a good product for legacy; for us, MongoDB is for legacy databases and legacy apps, and in this scope, it is a good pattern and a stable database engine; however, for new deployments and new applications, CosmoDB is a better engine.
What is most valuable?
My experience as a partner with Microsoft is very good because we have been a partner for three or four years, and it has been a very good experience.
MongoDB may have advantages over Cosmos DB perhaps in metrics because you can make some dashboards with database metrics, and there are many tools in MongoDB for dashboarding that are perhaps better than CosmoDB.
The dashboards in MongoDB have more functionalities; for example, you can create a dashboard with MongoDB database data, and it is simple to create, such as some sales dashboards, while I do not see this functionality to rapidly create such dashboards in CosmoDB.
What needs improvement?
While MongoDB is a good product, it is also an expensive product for support, and its scalability is acceptable, but the big problem with MongoDB is the cost.
For security in MongoDB, we work with encrypted databases by default, but we have not contracted the security options in our contract because it is too expensive, so we only implement encrypted databases without the security pack, which is very expensive for us; in security, we are at the first steps, just using encrypted databases.
I think additional features needed in MongoDB include perhaps vector databases, as I think they are not supported right now.
For how long have I used the solution?
I have been working with MongoDB for five years.
What do I think about the scalability of the solution?
The scalability in MongoDB is limited because we only work with ReplicaSet with two servers, and in comparison, the scalability in CosmoDB is much better than the MongoDB ReplicaSet models; although you can set the auto-provisioning of a node in ReplicaSet, it is very expensive, and we have to work with manual scalability in MongoDB.
The performance of MongoDB is good, especially in a ReplicaSet model, but if you want to pass on to another model, for example, Sharding models, it is very complicated; in ReplicaSet, it is acceptable, but if your workload needs more performance, and you must pass to a Sharding model, it is complicated in MongoDB, whereas in CosmoDB, it is simple.
What was our ROI?
We have seen a little ROI, and we want to target CosmoDB for this return on investment because it is the better model for this feature; however, with MongoDB, it is difficult to calculate the return on investment, as it is too expensive for our use.
What's my experience with pricing, setup cost, and licensing?
We pay approximately 2,000 euros per month for MongoDB.
What other advice do I have?
This solution receives a rating of 7 out of 10.
Leverages public cloud and ease to use but support response time requires improvement
What is our primary use case?
We used MongoDB on AWS for a specific project.
What is most valuable?
We put MongoDB on AWS for a specific project. It's easy to use.
What needs improvement?
If something is wrong on the cluster, then you need to contact the support team. The stability could be better.
For how long have I used the solution?
I used MongoDB for about a year.
What do I think about the stability of the solution?
It's okay. It's acceptable. The stability could be better.
How are customer service and support?
If something is wrong on the cluster, you need to contact the support team. At first, when we were trying to build a cluster.
How would you rate customer service and support?
What other advice do I have?
We rated MongoDB a seven out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Simple to learn and implement, but data consistency could be more efficient than traditional SQL
What is our primary use case?
I have used the product to store and manage data operations.
What is most valuable?
MongoDB is simpler to learn and implement than traditional SQL solutions like MySQL.
What needs improvement?
The product's data consistency could be more efficient than traditional SQLs.
For how long have I used the solution?
I have used MongoDB for a year while working on a project. I was using the latest version.
What do I think about the stability of the solution?
MongoDB was stable and much faster than traditional SQL.
What do I think about the scalability of the solution?
There were five MongoDB users in our organization working in different teams.
Which solution did I use previously and why did I switch?
I was working with MySQL before. I decided to use MongoDB rather than other products to learn something new. It is easier to learn and implement than other databases.
How was the initial setup?
The learning process for initial setup is easier compared to traditional SQL. Someone without prior experience working with it can learn the process quickly.
What's my experience with pricing, setup cost, and licensing?
MongoDB is an open-source product. We don't have to pay for the licenses.
What other advice do I have?
I advise others to evaluate a lot of other databases. MongoDB worked fine for my project. However, I would have selected a product besides MongoDB to improve my skills and learn something new.
I rate it a six out of ten.
Which deployment model are you using for this solution?
On-premises
