soveran

Hey Sam, currently we can support a great deal of customization, but we need to figure out how to best expose that. I think we will post updates to the Redis mailing list.

Thanks, we'll review the copy based on your suggestions.

Indeed, I mean "many" :-)

That's correct, it's hosted on EC2. We plan to host other instances on different cloud providers, to the same effect.

To check the pricing and the source code, check the announcement thread: http://groups.google.com/group/redis-db/browse_thread/thread...

Can you post the Redis configuration you are using?

redis-object is useful but it's not closer to Redis. In terms of functionality, it is comparable to Nest (http://github.com/soveran/nest), but because it translates Redis commands to Ruby syntax, it has 1026 lines of code vs Nest's 32. Ohm, which in your view is not close to Redis and more complex, is actually closer because it uses Nest to solve that problem (and it's just 764 lines of code, 262 less than redis-objects).

Ohm shouldn't be used for everything, but for the specific design pattern of mapping objects to Redis, it helps you to avoid coding errors.

Yes, works as expected.

Redis also manages URLs directly: Redis.connect('redis://localhost:6379/1') works as expected.

Redis understands URLs, so you can send it directly via connect:

    Resque.redis = Redis.connect(ENV["REDISTOGO_URL"])

Great idea, let's talk about it on IRC.