Until 1.7.5, the advice seems to have been that ANY single server is vulnerable, always use replication sets to prevent losing data.
While I appreciate that point, and we do use ReplSets for every DB, in the real world problems happen.
A circuit might explode in a DC, causing all the machines to go down. (Happened to me at ThePlanet)
Our Secondary machine might go down, and while fixing it, the primary might fail. (Happened two weeks ago on dev machines)
Our devs might run a test database on their Macbooks; While this isn't mission critical to stay up, potentially losing records means they need to restart all tests after an event, rather than resuming.
There's a million other places that this will be helpful. Yes, we should always spread things out as much as possible.. But I still use redundant power, RAID arrays, a journaled filesystem and in ideal times a ACID DB.
Until 1.7.5, the advice seems to have been that ANY single server is vulnerable, always use replication sets to prevent losing data.
While I appreciate that point, and we do use ReplSets for every DB, in the real world problems happen.
There's a million other places that this will be helpful. Yes, we should always spread things out as much as possible.. But I still use redundant power, RAID arrays, a journaled filesystem and in ideal times a ACID DB.Here's hoping 1.8.0 will be out soon! ;)