External reviews
503 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Critique de produit - MongoDB
Qu'aimez-vous le plus à propos de the product?
MongoDB est une base de données NoSQL qui a la capacité de gérer de grandes quantités de données non structurées. C'est une base de données flexible, c'est-à-dire sans schéma, ce qui nous donne la liberté de stocker des données de différents types que nous n'avions pas avec les bases de données SQL. Un autre avantage majeur que j'ai constaté avec MongoDB est le Sharding, qui nous permet de distribuer les grandes quantités de données sur plusieurs serveurs connectés à l'application. Un autre point important était l'évolutivité, car nous traitions de grandes quantités de données. C'est une base de données évolutive horizontalement.
Que n’aimez-vous pas à propos de the product?
Je ne dirais pas que je n'aime pas, mais cela dépend du cas d'utilisation que nous utilisons.
Premièrement, les JOINS ne sont pas pris en charge, ce qui est l'épine dorsale des bases de données SQL.
Une autre chose est la taille maximale des documents qui ne peut pas dépasser 16 Mo. Je ne comprends vraiment pas quel est le concept de cette limite.
Premièrement, les JOINS ne sont pas pris en charge, ce qui est l'épine dorsale des bases de données SQL.
Une autre chose est la taille maximale des documents qui ne peut pas dépasser 16 Mo. Je ne comprends vraiment pas quel est le concept de cette limite.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Nous essayons d'utiliser une base de données dont le schéma n'est pas fixe et peut être modifié au fil du temps, ce qui n'est pas facilement possible dans une base de données SQL. De plus, nous voulons gérer de grandes quantités de données non structurées et la plupart de nos services sont basés sur le cloud, MongoDB était notre meilleure option, je dirais.
Recommandations à d’autres personnes envisageant the product:
Si vos données ne sont pas structurées/planifiées/fixées, complexes à gérer et volumineuses, vous devriez opter pour MongoDB.
The integration went well and was lightweight
It is one of the main database back-ends for one of our products in the company.
How has it helped my organization?
* It has a flexible integration with our easy API.
* It has a good, easy integration with other tools that we use for this product.
What is most valuable?
* Flexibility
* An easy API
* Its redundance: We have a cluster of three very solid instances, so its very reliable.
* The integration went well and was lightweight.
What 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.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
We have good impressions of the stability.
We are good as far as the stress that we place on it. This is one part of the product that we are not worried about.
What do I think about the scalability of the solution?
The scalability is good. We use a three instance cluster for this installation, and it works great. Therefore, we haven't had to touch it for awhile, which is good.
How was the initial setup?
Our backups required some configuration.
Which other solutions did I evaluate?
I did not evaluate the product because I am on the operations side and the design was already done.
What other advice do I have?
Look at what MongoDB can do for you in terms of database back-end persistence. I would recommend to look at this first before you start looking at other solutions.
My company is interested in putting out products that are reliable for our customers, which we can monitor easily. We also want them to be easy to install and deploy, which is why I am happy with this one.
We are running this on an AWS instance.
It is nice because our developers create tables whenever they need to sync data
We use it for all of our temporary data, anything which is not warehoused.
It works with AWS Lamda and EC2.
How has it helped my organization?
It is nice because our developers create tables whenever they need to sync data. There are allocations nor DBAs. It is just use it as you need it.
What is most valuable?
* Autoscaling
* No overhead
* No maintenance
What needs improvement?
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.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
It is very stable. It has been running without issues.
What do I think about the scalability of the solution?
We have about 2000 customers a day.
What's my experience with pricing, setup cost, and licensing?
The pricing is good. We originally chose it over DynamoDB because of the pricing.
Which other solutions did I evaluate?
We also looked at DynamoDB from Amazon. However, it didn't have the features that we wanted from MongoDB.
We chose MongoDB based on its pricing and features.
What other advice do I have?
I have been happy with the service. Everything is good. Though, nothing stands out to me as exceptional.
I would encourage someone to look at DynamoDB, even though I am fine with MongoDB. If you are in a fully integrated into the AWS environment, you might want to stick with Amazon Web Services rather than a third-party.
Its most valuable features are high availability and zero maintenance
* High availability
* Resource recovery
How has it helped my organization?
It brought a lot of confidence to our team.
What is most valuable?
* High availability
* Zero maintenance, to double up things.
What needs improvement?
The cost needs improvement. The product is good, but the cost that we paid for it is expensive, so it wasn't that valuable.
For how long have I used the solution?
Less than one year.
What do I think about the stability of the solution?
The reliability is good.
What do I think about the scalability of the solution?
It is reliable. We have a small environment right now.
How was the initial setup?
The integration and configuration of this product in our AWS environment were easy and straightforward.
AWS works well with this application, but that is the only thing we have tested. We are happy with it.
What's my experience with pricing, setup cost, and licensing?
Purchasing through the AWS Marketplace was easy and seamless. We chose the AWS Marketplace because it is a brand name and a popular product.
It is too expensive. They need to work on this.
Which other solutions did I evaluate?
I also evaluated the open source version of this same product, but chose the AWS version for more reliability and enterprise support.
What other advice do I have?
I would recommend the product.
It was easy and quick to market in terms of getting the application deployed rapidly
It drives a good portion of our client-facing software utilities.
What is most valuable?
* Scalability is its most valuable feature, as it is pretty simple.
* The maintenance is fairly easy.
* It was easy and quick to market in terms of getting the application deployed rapidly.
What needs improvement?
The cost needs improvement.
For how long have I used the solution?
Three to five years.
What do I think about the stability of the solution?
The stability is fine.
How is customer service and technical support?
We use technical support quite frequently. The tech support experiences that I have heard anecdotally have been fine. I haven't heard about any issues of getting problems resolved.
We are mostly using technical support because of changes in deployments and learning how to configure new things. While a lot of the work is done in-house, it is more about extending the capabilities of our internal team.
What's my experience with pricing, setup cost, and licensing?
Pricing could always be better.
Which other solutions did I evaluate?
I am sure that they evaluated other products, but it's been in deployment since I have been with the company. Therefore, I don't know if they looked at other types of databases at that time.
What other advice do I have?
It is a great product. It works fine, so we recommend it. We are continuing to use and expand it.
Right now, MongoDB is deployed for a very specific use case. However, it is something that we always consider when we are looking to migrate away from traditional RDBMS, like Oracle and SQL Server, then MongoDB is on the top of that list. We see if it is capable of supporting the app as written.
I was not involved in the implementation or configuration.
Our queries are quicker with it. It is also very easy to use.
We use it for hosting data on the cloud.
How has it helped my organization?
It enables us to get work done quickly and get to our data. It benefits us by providing performance.
What is most valuable?
* As a user, it is very easy to use. There is nothing complicated.
* We can write queries and go through it very quickly; our queries are quicker with it.
* Many tools are there. Other companies are providing many tools for getting to your MongoDB.
What needs improvement?
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.
For how long have I used the solution?
Three to five years.
What do I think about the stability of the solution?
We are happy right now with stability unless something goes wrong down the line. In that case, you have to bite the bullet.
In terms of workloads, we put 60 to 80 percent on it.
What do I think about the scalability of the solution?
So far, so good. However, we have had issues with our VPC, and how we have stored on S3 and our instances that we have with MongoDB. We are learning as we are building more capacity.
Our environment is utility customers, which is millions of meters, and each one has their own instance. We obtain that data for every 15 minutes in a big city environment, which is why performance is very important.
How is customer service and technical support?
The technical support is good. We have received very good feedback.
How was the initial setup?
The integration and configuration were pretty easy. We loved it. Otherwise, we would have changed databases.
What was our ROI?
We have definitely seen ROI.
What's my experience with pricing, setup cost, and licensing?
The purchasing process through the AWS Marketplace was very good.
Which other solutions did I evaluate?
I was involved later on in the evaluation process when we were looking to import and export data out of MongoDB. We looked at MySQL, but we wanted to be on the cloud instead of managing our data on MySQL.
What other advice do I have?
I would recommend it. It is better than the legacy databases, and it is very good with the cloud.
meilleur à utiliser pour un MongoDB
Qu'aimez-vous le plus à propos de the product?
les idées sont les meilleures dans cela et la capacité de recevoir des alertes est également excellente. C'est vraiment précieux pour surveiller et dépanner en cas de problèmes.
Que n’aimez-vous pas à propos de the product?
MongoDB lui-même n'est pas si génial dans le cloud (AWS)... c'est cher, pas si optimisé et la liste continue.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Pour surveiller les performances de la base de données du pipeline de données. Réduire les erreurs humaines. Économiser du temps et de l'argent.
Recommandations à d’autres personnes envisageant the product:
Plus efficace Ops avec gestion de base de données automatisée est nécessaire.
MongoDB Cloud Manager Facile à Utiliser
Qu'aimez-vous le plus à propos de the product?
le changement de versions est très simple et fluide et cela prend très peu de temps. J'aime aussi pouvoir voir tous mes différents serveurs de base de données en très peu de temps. Une bonne stratégie de sauvegarde est une partie critique de tout système de gestion de base de données. MongoDB offre de nombreuses options pour les sauvegardes et la récupération/restauration. Avec une bonne méthode de sauvegarde, il est très important d'avoir plusieurs répliques de la base de données. Cela aide à restaurer la base de données sans avoir de temps d'arrêt, même d'une seconde.
J'ai également trouvé que les rapports et le temps réel sont très utiles, surtout pour déterminer les problèmes de serveur, ce qui m'aide beaucoup.
J'ai également trouvé que les rapports et le temps réel sont très utiles, surtout pour déterminer les problèmes de serveur, ce qui m'aide beaucoup.
Que n’aimez-vous pas à propos de the product?
Sur l'effet des coûts de taille des données.
Le processus de restauration lent.
Parfois, pour les bases de données plus grandes, le processus de sauvegarde peut être très gourmand en ressources.
Le processus de sauvegarde peut augmenter la charge sur le serveur pour ces raisons, donc vous devriez exécuter le processus de sauvegarde pendant la nuit ou les heures creuses.
Le processus de restauration lent.
Parfois, pour les bases de données plus grandes, le processus de sauvegarde peut être très gourmand en ressources.
Le processus de sauvegarde peut augmenter la charge sur le serveur pour ces raisons, donc vous devriez exécuter le processus de sauvegarde pendant la nuit ou les heures creuses.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Nous avons utilisé MongoDB Cloud Manager pour la restauration à un moment donné dans notre système. Pour nous, c'est la meilleure solution de sauvegarde continue et en ligne.
Recommandations à d’autres personnes envisageant the product:
Une bonne stratégie de sauvegarde est une partie essentielle de tout système de gestion de base de données. MongoDB offre de nombreuses options pour les sauvegardes et la récupération/restauration. Avec une bonne méthode de sauvegarde, il est très important d'avoir plusieurs répliques de la base de données. Cela aide à restaurer la base de données sans avoir de temps d'arrêt, même d'une seconde. C'est pourquoi MongoDB est recommandé.
L'une des principales bases de données ayant un grand impact
Qu'aimez-vous le plus à propos de the product?
Personnellement, j'aime la boussole et la transparence et la facilité de travailler avec des documents et des collections à travers les clusters.
Que n’aimez-vous pas à propos de the product?
Les ensembles de répliques se figent lorsqu'un énorme flux de données atteint le primaire.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Nous avons utilisé MongoDB pour une grande variété d'applications clients, à savoir, IoT (Suivi et sécurité des expéditions de conteneurs), applications énergétiques/environnementales, modélisation financière.
Recommandations à d’autres personnes envisageant the product:
et voir la différence
It was easy to validate data, access data, make active run queries against it, and retrieve data from it
I used it for testing.
How has it helped my organization?
It provided time saving for me. It provided an easy way to create validation against the database.
What is most valuable?
As a tester, it was easy to validate data, access data, make active run queries against it, and retrieve data from it.
What needs improvement?
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.
For how long have I used the solution?
Three to five years.
What do I think about the stability of the solution?
Except for the UI's stability, the product's overall stability is fine.
What do I think about the scalability of the solution?
The scalability is good.
How is customer service and technical support?
We did not use the technical support.
Which other solutions did I evaluate?
Right now, I'm using DynamoDB, and I preferred using MongoDB more.
What other advice do I have?
showing 51 - 60