External reviews
External reviews are not included in the AWS star rating for the product.
Powerful NoSQL DB
What do you like best about the product?
MongoDb is a powerful NoSQL DB and has become very performant with the addition of the WiredTiger storage engine. MongoDB is easy to setup and easy to work with in a variety of languages. Editing data is easy, since it is essentially modifying JSON.
What do you dislike about the product?
Joining data can be a bit hairy, so you have to make sure MongoDB is actually the correct solution for your use case. Querying can sometimes be confusing at first when wanting do more than a simple field match.
What problems is the product solving and how is that benefiting you?
We use MongoDB collections for storing a variety of content data that powers our website. An object can be a specific product or an article, or configuration data.
Recommendations to others considering the product:
Mongo is a great schema-less option that can allow you to dump your objects straight from your code as-is. This means not having to deal with normalization like in relational databases and having to do joins across collections, since all the data can be tied directly with the object. This requires a different mindset than when designing a relational DB-based project.
- Leave a Comment |
- Mark review as helpful
perfect DB platform for Big data analytics scaleout in the cloud!
What do you like best about the product?
Flexibility and scalability...Clearly the perfect DB platform for agile, fast speed to market development while dealing with scale based on commodity, redundant hardware is fantastic!
What do you dislike about the product?
A bit too open and immature (as compared to the RDBMS vendors) at times. If your developers are adult-like, Mongo is an awesome tool to support Agile/iterative development. If you struggle with rigors in the app-tier on data model consistency and enforcement, mongo won't help you much (until latest version).
What problems is the product solving and how is that benefiting you?
Internet of things data collection and big data scalability
Recommendations to others considering the product:
Make sure your developers are adult-like...otherwise go with a more seasoned veteran RDBMS like Oracle or MSSQL
Good for starters and heavy read applications
What do you like best about the product?
It's very easy to start with. The console commands are javascript based and a library for every major language officially supported. Great documentation for starters.
Secondary indexes are very useful for query optimization.
The self balancing and sharding out of the box is great for people wanting to write a scalable application based on a datastore without needing to know a lot about database scaling.
Secondary indexes are very useful for query optimization.
The self balancing and sharding out of the box is great for people wanting to write a scalable application based on a datastore without needing to know a lot about database scaling.
What do you dislike about the product?
On a write heavy load, mongo does not perform that well. Or well at all. The self balancing sharding kind of breaks down. Mongo keeps on trying to auto balance in the back ground but fails because of heavy write load.
Also the default _id field is used extensively for sharding internally so overriding that field causes all sort of scaling issues.
Also the default _id field is used extensively for sharding internally so overriding that field causes all sort of scaling issues.
What problems is the product solving and how is that benefiting you?
I have used mongo as a data warehouse and as a event storage system. One is a read heavy usage, other one is write heavy. The big pro is how easy and quick it is to setup and start using. Con is definitely it's inability to scale with write heavy load.
Recommendations to others considering the product:
If your application is read heavy, mongo is a great to get going. If it's write heavy, I would do some load testing before I go with mongo in production
Using for research in my Campus
What do you like best about the product?
Simple to qery and its performance is the best
What do you dislike about the product?
not listed in linux repositoy, like debian or ubuntu repositry or rhel or centos repository
What problems is the product solving and how is that benefiting you?
for sms gateway and system log. its so lighty.
Recommendations to others considering the product:
good for system log in your server adminsitration,its like use log file but in dbms
Non relational database MongoDB for multiple purposes
What do you like best about the product?
Since this is a non relational database it offers a different approach for storing data. It's a whole different world.
This db can be used for cache layers in large scalable systems. Can be used as well as an alternative database for web systems. In my personal experience I have used it and have seen it being used for large mobile apps.
This db can be used for cache layers in large scalable systems. Can be used as well as an alternative database for web systems. In my personal experience I have used it and have seen it being used for large mobile apps.
What do you dislike about the product?
The transition from relational databases to non relational like mongo can be hard sometimes, but once you get used, a learning curve that lasts about 1 month you will love it.
What problems is the product solving and how is that benefiting you?
To handle large amounts of data this db is a good option.
Recommendations to others considering the product:
If you need to scale a system, or store large amounts of data, this is a good option.
Excellent Document DB
What do you like best about the product?
Very easy to get started, with very simple tuning you can get good performance.
Designing the data model is pretty straight forward - match the document structures to your find patterns and you'l be fine.
Designing the data model is pretty straight forward - match the document structures to your find patterns and you'l be fine.
What do you dislike about the product?
default configurations may lead to data loss - not something you want to find out in Production.
We've had incidents were data was lost or corrupted due to the way the internal replication works.
These are real "corner-cases" but if you need 100% guaranty of your data it's an issue.
We've had incidents were data was lost or corrupted due to the way the internal replication works.
These are real "corner-cases" but if you need 100% guaranty of your data it's an issue.
What problems is the product solving and how is that benefiting you?
Our product mainly uses Mongo to store "resources" - mostly things that can be fetched by IDs.
mongo is also used as a staging area due to it's flexibility and performance.
Last but not least, Mongo stores our Audit information.
Mongo did all of the above without any issues.
mongo is also used as a staging area due to it's flexibility and performance.
Last but not least, Mongo stores our Audit information.
Mongo did all of the above without any issues.
Recommendations to others considering the product:
MongoDB is a very simple to use yet very powerful document DB.
It's main powers are at the 2 ends:
- the very simple use cases: configuration management etc.
- the very large scale use-cases, for when a single machine is simply not good enough.
Since mongo can scale tremendously with very little effort and gives good performance it's definitely worth considering.
One thing to note here is that most developers and many DBAs are used to thinking in a relational model and might find Mongo to be lacking in features such as JOINS and might even try to implement it on the application side.
- it's not directly related to Mongo as a product but to the fact that it might take an extra effort to make the mind switch to work in a way which is more optimal to Mongo.
It's main powers are at the 2 ends:
- the very simple use cases: configuration management etc.
- the very large scale use-cases, for when a single machine is simply not good enough.
Since mongo can scale tremendously with very little effort and gives good performance it's definitely worth considering.
One thing to note here is that most developers and many DBAs are used to thinking in a relational model and might find Mongo to be lacking in features such as JOINS and might even try to implement it on the application side.
- it's not directly related to Mongo as a product but to the fact that it might take an extra effort to make the mind switch to work in a way which is more optimal to Mongo.
Fantastic DB for all aspects of the technical lifecycle
What do you like best about the product?
Quick and easy setup for prototyping applications without overly worrying about data structures, strong integration with high quality frameworks like NodeJS and Meteor, great to use when your using Javascript within your stack. The latest version that allows for joins within the aggregation pipeline has been fantastic.
What do you dislike about the product?
How much flack MongoDB (and most NoSQL DBs) get when people try to use them without understanding their benefits
What problems is the product solving and how is that benefiting you?
Working heavily with the MeteorJS framework which is tied directly to MongoDB, not only do we use it in our production app we also use it for all of data analysis DB
Recommendations to others considering the product:
Ensure it meets your requirements, which I guess can be said of any technology, mainly that whatever framework your using integrates well with MongoDB and has all the functionality you need it to have. In particular, how important are lots and lots of joins?
Good Database for Big data processing
What do you like best about the product?
Great data store in for nosql data stores.
What do you dislike about the product?
reliability is one concern with the no sql databases. Hence need to be improved upon. Not sure if ACID might be applicable to ur usecase but thats something I dont rely on mongodb for
What problems is the product solving and how is that benefiting you?
I am trying Mongodb for some analytical datastore where delays are OK. I will not use Mongo db for transactions data though.
Recommendations to others considering the product:
- Use it for application where Delays are OK.
Use mongodb in the app control system setting because the way to build ourql commands is very simple and powerful. Especially great when operating on small teams and most important, mongodb needs no standardization when the information is held in a pole/data set.
Use mongodb in the app control system setting because the way to build ourql commands is very simple and powerful. Especially great when operating on small teams and most important, mongodb needs no standardization when the information is held in a pole/data set.
showing 101 - 108