Using Redis with Ruby on Rails (opens in new tab)

(jimneath.org)

81 pointsJim_Neath15y ago11 comments

11 comments

andrewvc15y ago

I actually like the redis-objects gem, which maps redis structures to ruby objects.

https://github.com/nateware/redis-objects

michaeldhopkins15y ago

Would you please explain why you prefer it to rb-redis?

andrewvc15y ago

redis-rb maps redis commands into the ruby namespace.

redis-objects is built on top of redis-rb and creates objects that are backed by redis, with operations like push, pop, etc. cleanly mapped.

In other words, it's a more ruby-like API.

I recommend reading the github README for redis-objects, it goes into a lot of depth.

1 more reply

Jim_NeathOP15y ago

I've never used redis-objects but it does look interesting. I'll have a play around with it tonight and update the post.

Thanks for the heads up.

Edit: updated.

caiusdurling15y ago

Nice intro piece. Especially liked the breakdown of data structures in redis, comparing them to Ruby.

igorgue15y ago

I really loved the "TL;DR: Redis is fucking awesome."

I started using Redis for a project with Node, and I loved the node_redis library because it's non-blocking :-)

koudelka15y ago

I'm working on bringing em-hiredis up to spec. If you want a similarly non-blocking ruby alternative. https://github.com/koudelka/em-hiredis

tptacek15y ago

Redis is absolutely beautiful for async networking; the protocol is extremely straightforward. It has completely solved my problem of persisting data from EventMachine programs in Ruby, too.

A couple hundred lines of ObjC got a generic Redis client and a special-purpose blpop client working for my Cocoa apps (I keep libevent in a thread there).

phlux15y ago

I would love to see performance info for a site running redis on top of FusionIO hardware.

pjscott15y ago

Redis' usual mode of operation is to keep the dataset in memory, making the FusionIO SSD hardware kind of redundant. With the new diskstore back-end, though, and really fast solid state drives, I bet that Redis could be really fast with a data set much bigger than memory.

j / k navigate · click thread line to collapse

11 comments

andrewvc15y ago

I actually like the redis-objects gem, which maps redis structures to ruby objects.

https://github.com/nateware/redis-objects

michaeldhopkins15y ago

Would you please explain why you prefer it to rb-redis?

andrewvc15y ago

redis-rb maps redis commands into the ruby namespace.

redis-objects is built on top of redis-rb and creates objects that are backed by redis, with operations like push, pop, etc. cleanly mapped.

In other words, it's a more ruby-like API.

I recommend reading the github README for redis-objects, it goes into a lot of depth.

1 more reply

Jim_NeathOP15y ago

I've never used redis-objects but it does look interesting. I'll have a play around with it tonight and update the post.

Thanks for the heads up.

Edit: updated.

caiusdurling15y ago

Nice intro piece. Especially liked the breakdown of data structures in redis, comparing them to Ruby.

igorgue15y ago

I really loved the "TL;DR: Redis is fucking awesome."

I started using Redis for a project with Node, and I loved the node_redis library because it's non-blocking :-)

koudelka15y ago

I'm working on bringing em-hiredis up to spec. If you want a similarly non-blocking ruby alternative. https://github.com/koudelka/em-hiredis

tptacek15y ago

Redis is absolutely beautiful for async networking; the protocol is extremely straightforward. It has completely solved my problem of persisting data from EventMachine programs in Ruby, too.

A couple hundred lines of ObjC got a generic Redis client and a special-purpose blpop client working for my Cocoa apps (I keep libevent in a thread there).

phlux15y ago

I would love to see performance info for a site running redis on top of FusionIO hardware.

pjscott15y ago

j / k navigate · click thread line to collapse