4 ms·
This article is an excellent articulation of the strengths and (fixable) issues with mongoDB. I like MongoDB a lot, and the improvements suggested would really
by paulsutter 15y ago
This article is an excellent articulation of the strengths and (fixable) issues with mongoDB.
I like MongoDB a lot, and the improvements suggested would really strengthen the product and could make me more comfortable to use it in more serious applications.
- madworld 15y agoHow is the global write lock "fixable" without a major rewrite of the codebase? Like the article suggested, it would be one thing if they did it for transaction support. In reality, from looking at the code, it seems like the global write lock came from not wanting to solve the hard problems other people are solving.
- geoffeg 15y agoDB-level locking is planned for MongoDB 2.2 which should be out within a few months. https://jira.mongodb.org/browse/SERVER-4328 https://jira.mongodb.org/browse/SERVER-4328
- spidaman 15y agoMeh, if your other option is to use PostgreSQL and get row level locks, a db level lock is still a fail.
- j-kidd 15y agoAnd here's a great post that provides some insight on how much effort has been put in by RDBMS vendors to handle locking: http://stackoverflow.com/a/872808 http://stackoverflow.com/a/872808
- paulsutter 15y agoA major rewrite of the core engine is exactly what's needed. Sounds like a fun project. If they don't do it, someone else will. Adoption is hard to replace. Modifying API's is really hard. Rewriting a core engine? Reasonable and in this case probably necessary given the issues. There are lots of people here who could replace that core engine and someone should if the MongoDB guys can't.
- deleted 15y ago[deleted]
- deleted 15y ago[deleted]