8 ms·
I like the way MongoDB describes the flaws in their own system, but places the blame (four) squarely on the customer, where it belongs. It wasn't a random fail
by SemanticFog 16y ago
I like the way MongoDB describes the flaws in their own system, but places the blame (four) squarely on the customer, where it belongs.
It wasn't a random failure or a sudden spike that caused the crash -- it was completely predictable growth. Foursquare had already experienced the problem once, and they had solved it. All they needed to do was monitor their growth and iterate that solution.
Sure, Foursquare could have had a better sharding algorithm, but that would only have put off the crash a bit longer. This is a very basic failure -- not monitoring a system that you know is steadily growing.
- SriniK 16y agoI think they mongodb guys are correct - it is an issue with app architecture and app monitoring failure.