3 ms·
Could you give us an idea of your workload? From what I've been told MongoDB breaks in really bad and silent ways when under pressure. And I mean "ignore write
by phn 10y ago
Could you give us an idea of your workload?
From what I've been told MongoDB breaks in really bad and silent ways when under pressure. And I mean "ignore writes without giving out errors" kind of bad.
- Kiro 10y agoLots of small writes (200-1000 a second at peak maybe) but only reads it on server start once a day. Honestly I don't know if it's failing already but it doesn't matter that much. I would prefer to use something more stable though.
- z0r 10y agosounds like postgres would be fine
- threeseed 10y agoAnd by told I take it you mean read on HN ? Because none of what you said is really all that true. MongoDB has never ignored writes without giving errors. You have always been able to check if the write failed. The issue I think you're referring to is the F_SYNC immediately to disk default. Which was changed many years ago and was never the default for any of the language clients. MongoDB is a great database in specific situations.
- phn 10y agoActually it is feedback I have from the data guys at work, not HN. And you may be right about that configuration, but I cannot remember the exact details of the discussion. Either way, don't get me wrong. I use MongoDB as well, and am quite fond of its aggregation framework. It's just not something that I catalog as "reliable and high performance" the way I do redis (which of course, also has limitations of its own).