3 ms·
I have worked on several projects that successfully used MongoDB over the past six or seven years now with three different companies. One project had over 5TB o
by dugdun 9y ago
I have worked on several projects that successfully used MongoDB over the past six or seven years now with three different companies. One project had over 5TB of data spread out over a couple of databases with numerous collections each, and no we didn't shard that database. We also didn't have any issues with accessing the data at that size. When I see negative stories around a technology, especially databases/data storage, I personally like to dig in to see if things are as bad as people say. All platforms can have issues (don't get me started on SQL Server and torn pages ;) ). Most of the negative press I've seen around MongoDB was from people not understanding the technology. Sure there were valid issues/bugs and some people might have lost data, but I don't think it was as widespread as some posts would have you believe (except for those running old versions accessible from the internet without proper authentication that is). Also a lot of posts that keep coming up are from several years back. MongoDB has changed a lot over the past couple years, and they continue improving the platform with each release. Bottom line, understand the platform before using it, learn it's strengths and weaknesses and you should have a successful implementation as well.
- jitix 9y agoMe too. One of my consulting gigs back in 2012 was based on MongoDB and the system is still working well in production afaik. The use case was to store complex documents but size wasn't an issue, nor was the global table lock (it was a law firm's document management system). But over the years people's opinions seem to have changed from neutral to outright hostile when I bring up MongoDB. Also I used mongo's map reduce framework back in the day for reporting, something that stored procedures are still lagging behind (based on my experiences in MySQL and Postgres)