12 ms·
Am I the only person that things the sheer number of people that have had scaling issues with mongo is a GOOD thing? I think it speaks to changing technology la
by vkjv 12y ago
Am I the only person that things the sheer number of people that have had scaling issues with mongo is a GOOD thing? I think it speaks to changing technology landscape and attitude towards data.
Many more people are collecting and working on larger data sets than they would have ever dreamed of years ago. I credit MongoDB, in part, to allowing developers to do this and encourage them to try. Sure it has it's limitations and may not be as great in areas as other databases, but, wow have a lot of people tried and succeeded.
tl;dr, If reverse survivor-ship bias is a thing, I think mongodb has it.
- tracker1 12y agoI've been pretty happy with mongodb overall for a few years now. It isn't always the best fit... but it's a very good fit for a lot of scenarios. Replication and sharding in mongodb is way easier to get started with than most databases, and the failover for replication is very good as well. Though understanding how it works is still advised. Such as not having more than X nodes voting for electing a leader in case of failover, etc. That said, there are situations I'd be more inclined to reach for ElasticSearch, Cassandra or others. As soon as RethinkDB has it's automatic failover story in place, I'd put it above MongoDB though, slightly nicer developer interface, and admin is much nicer than others. Then again, if PostgreSQL got replication with failover in the box, I'd probably use that far more.