Hi Alejandro,

Last time I was looking into this I used
https://github.com/tphipps/kannel-redis
Hope it helps, until Toby replies with more updated resources.

Br, Rinor



On Wed, Feb 20, 2013 at 5:37 PM, Alejandro Guerrieri <
alejandro.guerri...@gmail.com> wrote:

> Hey Toby, I just came across this old email regarding Redis. Are you still
> using it? Any thoughts?
>
> I'd love to take a look at the code and play with it a little bit if you
> don't mind. I've been testing Redis for other purposes and I think it makes
> a lot of sense to use it for DLR's (and even the message store, with major
> changes in the way Kannel uses the store itself, but that's another story).
>
> If you can send me the patches (or whatever you have available) I'd love
> to take a look.
>
> Thank you in advance,
>
> Alejandro
>
>
> On Thu, Mar 24, 2011 at 3:12 PM, Toby Phipps 
> <toby.phi...@nexmedia.com.sg>wrote:
>
>> Hi all,****
>>
>> ** **
>>
>> Has anyone put any thought into implementing Kannel DLR storage (and the
>> basics of sqlbox MT injection) in a NoSQL datastore?  We are using Redis (
>> http://redis.io) for other projects and are very happy with it. Its
>> key-based storage/retrieval and strong support for arrays as atomic queues
>> would make it perfect for Kannel, especially given the transient nature of
>> this data and Redis’ memory speed with disk backing. ****
>>
>> ** **
>>
>> The main advantages in my mind are that during heavy loads disk access
>> would be minimized, DB polling would disappear (to be replaced with
>> blocking array pops) and the SQL overhead would be removed replaced with
>> set/fetch by keys.****
>>
>> ** **
>>
>> No particular reason this would need to be Redis – memcached, MongoDB,
>> Cassandra etc. would also probably work well assuming they have the
>> array/queue support.****
>>
>> ** **
>>
>> Any thoughts? It wouldn’t be a small project, but basing the code on the
>> existing implementations of SQL DLRs and sqlbox would mean  a big jump
>> start…****
>>
>> ** **
>>
>> Toby.****
>>
>
>

Reply via email to