Re:LocomotiveCMS Approaches 2.0 Release
by runako on Tuesday April 17, 2012 @12:47PM
(#3853503)
I'm not well-versed in Mongo, but it seems like the comment was saying that he didn't trust Mongo to handle any writes. Your response seems to say that since there aren't many writes to lose, it's okay. Does that concede that Mongo will lose data? (I didn't know that about Mongo.)
[ Parent
| on HN ]
To explain the parent comment, in a write heavy application, you would probably want to turn off transactions in Mongo in return for the performance gain.
What the comment you're responding to is saying is that when you aren't making many writes, you can afford to switch transactions on and have Mongo lock the whole database because the odds of having a read come in at the same moment are much lower than if you were making a write every second.
Ahh, thanks for the explanation. This clears up something I didn't know about Mongo (next to nothing other than that the other commenters all seemed to indicate that it should not be used for writes).
Much more informative than a downvote.