News for hackers. Stuff that matters.
Re:What 10gen nailed with MongoDB by ihsw on Wednesday August 29, 2012 @04:45PM (#4451059)
One of the main sticking point for serious mongodb infrastructure is the global lock -- yes, write operations cause the entire mongodb instance (every database, every read operation) to block. This is clearly one of the main issues surrounding high-concurrent mongodb development.

Thankfully with mongodb-2.2 there is now instead a database lock which mitigates the issue.

Personally I feel redis more closely resembles language primitives with simple key-value pairs, hashes, lists (ordered, repeating values allowed), sets (un-ordered, no repeating values), and sorted sets (more interesting).

Re:What 10gen nailed with MongoDB by taligent on Wednesday August 29, 2012 @05:04PM (#4451235)
Redis has no clustering (yet) so is best used when your data is transient and you are able to repopulate.
Re:What 10gen nailed with MongoDB by j-kidd on Wednesday August 29, 2012 @08:53PM (#4452301)
I have no experience with Redis or MongoDB, but your statement is only true if the storage layer is transient. Some of us use servers that don't go away upon shutdown, backed by a SAN.
Re:What 10gen nailed with MongoDB by mh- on Thursday August 30, 2012 @12:45AM (#4453016)
Have you tested how long it would take your redis instance to be usable again after it finishes replaying the commitlog (AOF)?