I have an application that runs on Ubuntu Linux 12.04 which needs to store and retrieve a large number of large serialized objects. Currently the store is implemented by simply saving the serialized streams as files, where the filenames equal the md5 hash of the serialized object. However I would like to speed things up replacing the file-store by one that does in-memory caching of objects that are recently read/written, and preferably does the hashing for me.
The design of my application should not get any more complicated. Hence preferably would be a storing back-end that manages a key-value database and caching in an abstracted and efficient way. I am a bit lost with all of the key/value stores that are out there, and much of the topics/information seems to be outdated. I was initially looking at something like memcached+membase, but maybe there are better solutions out there. I looked into redis, mongodb, couchdb, but it is not quite clear to me if they fit my needs.
My most important requirements:
- Transparent saving to a persistent store in a way that the most recently written/read objects are quickly available by automatically caching them in memory.
- Store should survive a reboot. Hence in memory objects should be saved on disk asap.
- Currently I am calculating the md5 manually. It would actually be nicer if the back-end does this for me. Hence the ability to get the hash-key when an object is stored, and be able to retrieve the object later using the hashkey.
- Big plus is that if there are packages available for Ubuntu 12.04, either in universe or through launchpad or whatever.
- Other than this, the software should preferably be light not be more complicated than necessary (I don’t need distributed map-reduce jobs, etc)
Thanks for any advice!
I’d look at
MongoDB. It caches things efficiently using your OS to page data in and out, and is pretty simple to setup. Redis and Memcached won’t be good solutions for you because they keep everything in RAM. Other, simpler solutions like LevelDB or BDB would also probably be suitable. I don’t think any database going to compute hashes automatically for you. It sounds like you already have code for this though.