[loginalready]

You just answered your own question. Their customers are developers, i.e., a scarce and expensive resource who's time is most effectively spent developing rather than configuring, tuning, monitoring and otherwise maintaining server parks, virtual or not.

[nasalgoat]

But redis doesn't really require any of that - it'll run and provide decent performance on a small instance, or even better, running on the same instance your app is running.

"yum -y install redis" then "service redis start" and it just works. I'm not sure there is an easier service to use than local redis.

[jefe78]

Interesting concept, but how does that scale?

[nasalgoat]

Scale? I thought the use case was modest load?

Either way, I do 30K/sec queries on a single redis instance on a small instance - the performance is quite exceptional.

[jefe78]

Fair enough. 30k/sec sounds pretty nice. Sadly, I imagine that's a local instance. We need a solution that can handle orders of magnitude more than that though. Which, from my understanding, means multiple instances. And I have no experience with scaling Redis. I'd kill for a good turn-key solution.

Edit: Someone contact me. I want to give you money!

[rohitnair]

I have no personal experience using redis-cloud, but their website[1] does give a good overview of their features. Currently, redis has no native clustering/sharding support AFAIK, but cloud based services like redis-cloud seem to be offering exactly that, in a very transparent way. It also seems to be taking care of monitoring, backups etc.

[1] - http://redis-cloud.com/redis/redis-comparison

[_bpo]

As a representative from one of the competitors mentioned there, I can tell you that feature list is dishonest and absurd.

When someone offers you "infinite scale", run.

[_bpo]

Hi there,

I'd love to help you. We (RedisGreen) run extremely high-performance, dedicated Redis installations and work directly with customers to help tune their app and their installation for the best possible service.

Getting Redis up and running is easy, as has been mentioned in this thread. But the devil is in the details. Third-party vendors distinguish themselves in terms of active monitoring, quality/knowledge of support, and closed-source features (e.g. one company offers what they call "multicore Redis").

I've been running large-scale production instances of Redis since 2009, and our other team members are similarly qualified.

I'd love to help you out and give you honest recommendations on system scaling. bpo at stovepipestudios.com

[nasalgoat]

Actually, I have several TBs of redis capacity online and run millions of queries a second against it. I was speaking to a simple use case.

A bit of googling will answer most of your redis scaling questions.