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
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?