News for hackers. Stuff that matters.
Re:MongoDB adds atomic find and modify by old-gregg on Thursday December 31, 2009 @08:41PM (#1025331)
Isn't that defeating the purpose of MondoDB? We're considering switching to it precisely because we're sick of two-tiered approach (MySQL+memcached) and MongoDB promises a built-in near-realtime caching.

Why would I want to lose the power of SQL if I'm not getting anything in return? I thought that "built-in memcached" was what I'd be getting. No?

Re:MongoDB adds atomic find and modify by delano on Saturday January 02, 2010 @04:53PM (#1027722)
Storage and caching are two different problems so it's reasonable to assume two separate solutions.

In this case, MongoDB is a leap ahead of MySQL; Redis is a leap ahead of Memcached. Both solve the core problems very well and include additional freebies (MongoDB's high-performance aggregate functions and Redis' atomic increments and set and list functions).

Re:MongoDB adds atomic find and modify by cloudhead on Friday January 01, 2010 @04:37AM (#1025580)
mongodb doesn't do concurrency very well -- at least not as good as Redis.
Re:MongoDB adds atomic find and modify by old-gregg on Friday January 01, 2010 @12:30PM (#1025939)
I looked up your profile but didn't find any contact info. I am dying to know more about MongoDB limitations and this page isn't helping:

http://www.mongodb.org/display/DOCS/Concurrency

Re:MongoDB adds atomic find and modify by dm_mongodb on Sunday January 03, 2010 @03:13PM (#1029026)
concurrency is much better in the newest versions