memcached "backends" (was Re: Simple questions from memcachednewbie)

[Randy Wigginton]

The problem with BDB, and the reason MySQL works out to be so much  
faster, is if there is a "catastrophic event", the data is still  
stored.  With BDB I had to specify to "synchronize" with the file  
system.

On Oct 12, 2006, at 5:04 PM, Jehiah Czebotar wrote:

> On 10/12/06, Jeetendra Mirchandani <jeetum at gmail.com> wrote:
>> In such a scene, losing a memcached instance means losing data, a lot
>> of it! Hence I would want to back up the data to mysql or bdb or a
>> similar persistent store.
>
> Then you should check out Tugela Cache as Garth already mentioned in
> this thread. It is a drop in replacement for the memcached server side
> and stores things in a BDB file, so you don't loose data across
> restarts.
>
> ie: you still use the same memcache client libraries; aka "drop in"
> replacment for the server
>
> http://meta.wikimedia.org/wiki/Tugela_Cache
>
> -- 
> Jehiah at gmail.com
> http://jehiah.com/
>