Reputation: 422
I am writing a web application where more users can perform simultaneous operation in the same document in mongodb. I use the mean.io stack, but I am quite new to it. I was wondering how does mongoose manage concurrency. Every "user click" operation performs first a read to get the document, and a save after some calculations. Of course the sequence read-calculate-save is not atomic. Does mongoose work with 'last change wins' policy, or does it throw a versioning error? Does it make sense in this case to use a queue?
Thanks, best regards.
Upvotes: 6
Views: 4780
Reputation: 589
Yes the last change will win.
A queue could be a good option to solve the problem but I'll suggest 2 other ways:
Upvotes: 6