21–28 of 28 posts
MongoDB is definitely ready and capable of handling your traffic. There are best practices to follow, however, as is the case with any deployment. I would concur with mattbillenstein that HN definitely skews anti-mongo. There are many, many companies using MongoDB very successfully. I have found that "issues" being reported with MongoDB are based on old versions and information, or an improperly configured and tuned…
Another user of MongoDB here. Thus far it has scaled well for us where we had a similar situation where uptake was faster then expected. The WiredTiger storage engine made most of the concerns of 2012-2013 for MongoDB, non-issues. However, if you try to put a relational model in to MongoDB, you still may see performance issues down the road, but then again it should be about the right tool for the right job. I'd reit…
HN skews very anti-mongo, but it can be a good fit for certain apps -- I would stick with what you know until you think you've outgrown what you can do without sharding. I'd probably never shard mongo, but if you can vertically scale it for awhile, I'd do that. If you're on ec2, the i3 instances have very fast nvme instance storage at a reasonable (cloud) price.
What would you suggest instead of mongodb for large scale production db? Our DB size is growing on daily basis and currently near to 200GB on a dedicated machine.
I recommend you learn at least one alternative database paradigm (relational/SQL databases are probably a good choice) so that you can make informed decisions about the trade-offs between data stores each time you start a new project.
HN skews very anti-mongo, but it can be a good fit for certain apps -- I would stick with what you know until you think you've outgrown what you can do without sharding. I'd probably never shard mongo, but if you can vertically scale it for awhile, I'd do that. If you're on ec2, the i3 instances have very fast nvme instance storage at a reasonable (cloud) price.
What would you suggest instead of mongodb for large scale production db? Our DB size is growing on daily basis and currently near to 200GB on a dedicated machine.
The hatred and fear of Mongo is justified. That doesn't necessarily mean you need to switch right now. If you're just using a document DB instead of a relational DB, you won't have a hard time moving away from Mongo. There just isn't that much to learn. Even better, there are various databases that actually have Mongo compatibility[1][2], but internally will be more reliable and scalable. If you have the dev bandwidt…
Great. I haven't built anything yet so I could just start out with one of these from the start. Thank you so much!
Another user of MongoDB here. Thus far it has scaled well for us where we had a similar situation where uptake was faster then expected. The WiredTiger storage engine made most of the concerns of 2012-2013 for MongoDB, non-issues. However, if you try to put a relational model in to MongoDB, you still may see performance issues down the road, but then again it should be about the right tool for the right job. I'd reit…
Thanks so much! We currently use Atlas and it's been pretty great, although prohibitively expensive for my small side projects, where mLab instead has been awesome.