Caching large objects in NoSQL stores is usually not a good idea, because it is expensive in terms of memory and network bandwidth. I don't think NoSQL solutions shine when it comes to storing large objects. Redis, memcached, and most other key / value stores are not explicitly designed for this.
If you want to store large objects in NoSQL products, you need to cut them into small pieces and store the pieces as independent objects. This is the 10gen saved approach for gridfs (which is part of the standard MongoDB distribution):
See http://docs.mongodb.org/manual/applications/gridfs/
To store large objects, I would rather look at distributed file systems, such as:
These systems are scalable, highly accessible, and provide file and object interfaces (you probably need an object interface). You can also refer to the following SO query to select a distributed file system.
Best distributed file system for linux merchandise storage farm
Deploy a cache on top of these scalable storage solutions.
Didier spezia
source share