2 posts tagged “oss”

Although its been a week or two since my multi-storage modification was announced in the memcached mailing list (thanks Brian), figured I should write my thoughts and not just code on this matter.

The aim simply is to achieve a network platform that can be widely used in the web industry. By meaning "network platform", I am trying to emphasize that what can be plugged to memcached doesn't necessarily need to be a storage engine.

For example, you could plug a task-queue engine that will periodically perform the tasks in the queue. Representing a task with a <key, value> pair is fairly straight forward since we can use something along the line of <task_type, related_data>. Since we are not using a hash structure but a queue for this example, you don't have to worry about overwriting the previous task(s) that you registered with what used to be the "key" ("task_type" in this example). Hmm.. come to think about it, you can probably use append to do this too.

This is the beauty of making memcached modular. The module writer has control over what to do with data that memcached receives from the client.

What I've mentioned so far are just bonuses from achieving modularity. For my personal use/hobby, I want to link memcached to a fast hash storage engine (Tokyo Cabinet is my favorite at the moment) and use it for fast persistent storage.

So yeah, though the patch that is floating around atm is only my initial attempt, I've managed to get the idea in shape since discussing this idea with Brian Aker last year in Tokyo. l seem to have several people in the community interested and like Dormando has stated, hopefully we'll have something exciting for version 1.4 :-)