title: Serialization "isolation level" in MongoDB, or the lost-update problem
body: <p>I realize MongoDB is a NoSQL solution, but I was wondering if it had some sort of equivalent to serialization-level transaction isolation level.</p>
  
  <p>If not, how would you solve the lost-update problem in MongoDB?</p>
  
  <p>I want to keep the revision history of some data in Mongo and each revision has to point to the one before it. How can I make sure no more than one latest revision exists for my data, and on the other hand that no revision is lost due to concurrent updates?</p>
  
  <p>** Edit **</p>
  
  <p>Oops, RTFM, it is indeed possible: <a href="http://www.mongodb.org/display/DOCS/Atomic+Operations" rel="noreferrer">http://www.mongodb.org/display/DOCS/Atomic+Operations</a></p>
  
  <p>Not sure if I should close the question since the knowledge might be relevant to other people..</p>