3 ms·
That doesn't actually guarantee the write was written to disk unless an fsync was issued. Of course that comes with a significant effect on MongoDB's famously
by brndnhy 15y ago
That doesn't actually guarantee the write was written to disk unless an fsync was issued. Of course that comes with a significant effect on MongoDB's famously marketed write performance.
- hogu 15y agoyes but the redundancy you have to use with mongodb gives you a very low probability of that type of failure.
- brndnhy 15y agoThen in MongoDB's case durability is a function of scale, which leads back to the parent's suggestion that it is a technology optimized for performance. Personally I think this is a bad foundation for data that is important. There are probably a lot of use cases where data not being on disk for n seconds (or one minute in the case of MongoDB) is ok. Even when that is the case, I still think that is the most important question to be addressed when choosing MongoDB as a data store. The flexible query API, schema-less document format, secondary indices... those are siren songs of rapid development.