5 ms·
Am I the only one using MongoDB who think it works great? I'm really happy with it.
by Kiro 12y ago
Am I the only one using MongoDB who think it works great? I'm really happy with it.
- larsmak 12y agoYep, no problems here. 80GB dataset, indexes are around 10GB, one master, two replicas. Lots of reads, all writes are done in bulk during the night (low read throughput). We also use Cassandra and postgresql a lot - there's no silver bullet when it comes to storage systems.
- thijsc 12y agoWe're really happy with MongoDB too. Can't wait to see how these improvements will work out for us.
- 127001brewer 12y agoI have been developing with MongoDB for about the past year. (Briefly, I have developed, and continue to support, an ASP.NET MVC C# Web Application that's used by a few thousand people daily. For my personal projects that use MongoDB, I develop with PHP and Python.) Overall, I enjoy working with MongoDB, because it (generally) maps directly to your object - there is no need for an additional layer (such as an Object Relational Mapper (ORM)). However, you have to be more careful with your data structure. For example, having sub-arrays in sub-arrays is probably not a good idea. I will be happy to share more, so feel free to look up my profile.
- msandford 12y agoI ran a website and operations for a company that did over 1mm a year in revenue. Everything was done off of a single machine that was the webserver, database server and media server. Had 10k customers all of whom were active daily. Postgres and Python/Django and I never saw load averages much over 10%. Unless you have a substantial fraction of a million daily users you probably don't need mongo.
- 127001brewer 12y agoI agree with that MongoDB may have been overkill, but my web application's architecture was chosen before I joined the team.
- jsjohnst 12y agoYou are still in the honeymoon period. Wait till you scale enough to start running into issues and you will then likely change your tune.
- functional_test 12y agoThis is objectively false. I used MongoDB for >3 years with 100% production uptime and a very large data set. I get that some people have had bad experiences with Mongo. Sounds like you're one of them. Why not share your experience rather than just spread FUD? It's worth noting that a lot of the complaints people had about Mongo were with things that were clearly documented (e.g. no confirmations on writes by default back in the day).
- Xorlev 12y agoWhat's a "very large dataset?" We started having issues around 100GB that forced an upgrade to SSDs. That lasted us til 2TB, at which point we switched.
- nemo44x 12y agoWhat else did your config have? Did you use RAID on your HD's? How much RAM did you have? What types of CPU's and how many? Were you updating documents often or writing new ones? Did you have compound indexes built properly? What was your latency requirements? Was MongoDB able to saturate your resources? Did you read off of secondaries at all? Did you shard your DB and if so what was your shard key? Was it random? Could you use it for reads too? How much of your data set did you need to possibly use at any given time? If you had to "upgrade to SSD's" at 100GB you either had amazingly poor provisions, were doing most everything wrong or both. Messages like yours indicate to me a poor user - not a poor database.
- Xorlev 12y agoOur config was pretty standard for a few years ago (~2011-2013). RAID10 7200RPM disks, I believe they were Sandybridge, 32gb RAM. We did a decent number of updates/s. 10gen couldn't find fault with our setup other than our need to do updates. Which is weird, updating a database? Inconceivable. Anwyays, spinning disks apparently couldn't deal with the seeking. Our lock percentage was incredibly high, which makes sense given our "high" write load. It was during this evaluation that we found many of their "critical statistics" were non-deterministic (like the padding factor, rerun and you get all values 0.0-2.0. Probably fixed by now). We had 1 index: primary. We did no other lookups. MongoDB managed to saturate only the IO subsystem. We did read from secondaries, but that didn't help overly much given that the write percent was high on them too. On their recommendation we upgraded to SSDs. That dropped our lock percentages and it stayed low. We never made it to sharding because we simply stopped caring about MongoDB. I inherited it and was responsible for it, but ultimately decided to get rid of it in favor of Cassandra. It's not a "poor user" when you follow their best practices of the time and have a poor experience. It (is|was) a poor database. The storage engine was braindead, their acquisition of WiredTiger admits that. It's at least improving, ever so slowly.
- larvaetron 12y agoSame here, we've been using MongoDB in production since 2011 (v1.8) and our experience has been outstanding. Looking forward to the improvements in 3.0.
- more-entropy 12y agoI'm not really happy with it, but it works well for me in two projects. In first one, Mongo acts as a huge distributed (multisharded), replicated file storage — we're using GridFS to store tens of millions files with tons of searchable metadata. In the second one it is just a backend for geo tracking software.