65 ms·
I think in the near future Mongodb will no longer have a global write lock. Yeah but I feel their pain. Given my still limited experience with it, Mongodb may b
by chaostheory 14y ago
I think in the near future Mongodb will no longer have a global write lock. Yeah but I feel their pain. Given my still limited experience with it, Mongodb may be great for reads, but not so much for writes.
- achompas 14y agoEDIT: deleted b/c I didn't make my point clearly.
- taligent 14y agoCall me stupid but I can imagine that losing data is a problem for a database company. That said MongoDB has a simple flag which allows you to choose how to handle writes. The app can 'wait' for writes to be applied to one node, all nodes, some number of nodes etc.
- achompas 14y agoHeh, that probably wasn't phrased well. Let's try again: Dynamo (and thus Cassandra) is designed for write speed and durability. What is MongoDB designed for?
- chaostheory 14y ago(assuming you're talking about safe writes opposed to normal writes) then you kill performance... which was one of the main reasons for switching to mongodb in the first place
- ra 14y agoIt would be better for the conversation if you edit to clarify your point rather than delete...
- taligent 14y agoMongoDB doesn't have a global write lock. It has a per collection lock and is moving towards per row locking.
- nodesocket 14y agoI don't think that is correct. Version 2.2 (beta) has database level locking, but that was the hard part. Collection, and document locking are coming after according to this talk by the CEO Dwight Merriman. (http://www.10gen.com/presentations/concurrency-internals-mongodb-2-2 http://www.10gen.com/presentations/concurrency-internals-mon...)