Re:MongoDB adds atomic find and modify
by delano on Thursday December 31, 2009 @01:44PM
(#1024729)
Interesting. In my most recent projects, I've been using MongoDB together with Redis. MongoDB for long term data (like records and reports) and Redis for near-realtime stuff (queuing, request limiters, analytics, and the like). I haven't come across the need for atomic record modification but that isn't to say there aren't useful usecases. I need to think on it a bit more.
[ Parent
| on HN ]
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?
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).
mongodb doesn't do concurrency very well -- at least not as good as Redis.
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:
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
Re:MongoDB adds atomic find and modify
by dm_mongodb on Thursday December 31, 2009 @01:50PM
(#1024741)
this touches on some related aspects: http://blog.mongodb.org/post/307919034/partial-object-update...