MongoDB Review
What do you like best about the product?
Sharding and Load-Balancing. MongoDB queries can be much faster in some cases, especially since your data is typically all in once place and can be retrieved in a single lookup
What do you dislike about the product?
No Joins, Concurrency Issues, Memory Usage
What problems is the product solving and how is that benefiting you?
One database that allows users to maintain the benefits of relational databases while incorporating innovations of NoSQL databases
data engineer
What do you like best about the product?
ease of upgrades and ease of scalability
What do you dislike about the product?
rs.reconfigs causing unnecessary outages even when they are not supposed to for example removing a dead member from the set
What problems is the product solving and how is that benefiting you?
performance
Nice Database!
What do you like best about the product?
Ability to scale, and cross platforms, security.
What do you dislike about the product?
It is too early to tell, i just started using and learning about Mongodb.
What problems is the product solving and how is that benefiting you?
We would like to move from legacy software, into a newer platform.
Great for Small/Medium companies with no dedicated DBA resource
Great for small to medium size companies with small infrastructures who don't necessarily need/want a DBA and have developers who prefer to spend their on writing code than managing MongoDB infrastructure. It's very easy to use and well layed out, providing a good array of monitoring metrics.
I'd say it's also good for proof of concept projects or sandboxes which are spun up and shut down once the need for them has gone.
At the moment it doesn't provide any of the enterprise level features than a more mature IT organisation would normally need/like (data encryption, auditing...etc). The larger your MongoDB estate is and the larger your data then the more expensive it becomes compared to running your on MongoDB estate in the cloud (both hardware and backup costs)
You're also limited in the instance types you can use and also the number of servers. For example do you really need a 3 node replica set for your test environment? Load Test and Prod for sure but for Test I'm not really sure this is required, so depending on how big your estate is you've just tripled your cost of this environment. If you want to shard you have to commit to fairly expensive larger instances, where I thought one of the pro's of sharding was that you could scale out over commodity hardware.
Hopefully it will become more feature rich as the product matures.
Decent for non-rapid database calls
What do you like best about the product?
Fast NoSQL results, easy setup, easy configuration.
What do you dislike about the product?
Read/write locks become a bottleneck. Replication authentication is tricky.
What problems is the product solving and how is that benefiting you?
We use MongoDB for our messaging system. I used it in a project previously for location mapping, their Geo location support is amazing.
Recommendations to others considering the product:
Consider other NoSQL databases
mongo as utility to hold large data
What do you like best about the product?
holding a generic large scale of data in mongo-db
What do you dislike about the product?
the documentation is not very clear/updated
What problems is the product solving and how is that benefiting you?
holding large scale of data
Recommendations to others considering the product:
it is a very good utility to hold large data but searching in this data is not very fast
MongoDB Review
What do you like best about the product?
Mongo is very easy to get up and running. I also enjoy working with the dynamic non-relational JSON collections. It is quick and easy to work with which makes it great for rapid prototyping. The database is also entirely free.
Another aspect I enjoyed about using Mongo was the availability of free educational resources. I enrolled in MongoDB for .NET developers which quickly got me up to speed and I was able to quickly start working efficiently with Mongo at work.
What do you dislike about the product?
The collections used in Mongo don't have support for joins, so if you're working with very large sets of data where you need multiple joins, you may be better off with a relational schema.
What problems is the product solving and how is that benefiting you?
I currently use Mongo as a document storage repository and it has been great thus far. Since I am only working with documents, and not multiple large sets of data, the dynnamic JSON collection structure works very well for this.
Recommendations to others considering the product:
I recommend Mongo to any developer. It is very quick and easy to pick up with only a small learning curve. Also great for rapid prototyping and for putting together a proof of concept. Mongo is also great for scalability with the concept of automatic sharding as the amount of data in your database continues to increase.
