Re:
by saurik on Monday June 04, 2012 @07:56AM
(#4063577)
FWIW, they only just dropped the global server lock, and they replaced it with a per-database lock; not per-object (which would be analogous to what most databases have: row-level locking) or even per-collection, but per-database (which honestly is only non-global by technicality).
In all seriousness, it is not that the behavior now is reasonable and is finally fixed, but that the behavior before was so outlandishly absurd (what possible legitimate reason is there to have cross-database locking?) that the new behavior only seems reasonable in comparison. ;P
Hey look another I picked a tool and didn't know how to use it post about MongoDB made it to the front page in less then a half hour. The five people who promoted this thing , did you even read the article ? There is nothing in here that is even close to being noteworthy. Next up on the front page. Small company has a segmentation fault on linux and decided to switch to BSD.
All of these caveats have been known since MongoDB was first invented so not sure why you would use it for several years and THEN decide to switch.
And they are being addressed. For example the global write lock is now only per database and the next release it will be per collection. Likewise map reduce is an ongoing area of improvement. Not sure how Hadoop integration reflects badly on this.
Anyway many of those points are design decisions so if your needs aren't being satisfied use something that will work. God knows do your research before deployment because switching is going to be a lot of work.
It's gone
* The query engine of MongoDB still can only use of one index per query. How insane is this?
MySQL uses one index per query and it's fine with that. What else do you want? It's a tree index, there's no any magic there.
* Having no option to perform an operation comparable to UPDATE table SET foo=bar WHERE..
In fact, you have that option. That's what modifier operations are for.
* there are already too many moving parts in a setup for scalable applications.
Oh my god! Creating scalable applications is hard! I thought MongoDB would do that for me, but it did not.
I think that no-nosql hype is even worse than nosql hype. That's when you suddenly realize: no, it's NOT WEBSCALE.
In all seriousness, it is not that the behavior now is reasonable and is finally fixed, but that the behavior before was so outlandishly absurd (what possible legitimate reason is there to have cross-database locking?) that the new behavior only seems reasonable in comparison. ;P
And they are being addressed. For example the global write lock is now only per database and the next release it will be per collection. Likewise map reduce is an ongoing area of improvement. Not sure how Hadoop integration reflects badly on this.
Anyway many of those points are design decisions so if your needs aren't being satisfied use something that will work. God knows do your research before deployment because switching is going to be a lot of work.