Hacker News Reader

Have to disagree with this. Redis is dead simple to install and configure out of the box.

This seems like a solution to a nonexistent problem.

I would add a seemingly expensive solution to this non-existant problem. It may kind of makes sense for heroku because afaik they don't offer redis support out of the box.

Yeah, I would definitely consider using the $25 plan with Heroku. The only other real option is to run Redis on its own EC2 instance, which costs $62 minimum (well, once you're sure the thing's sticking around, you could make it a reserved instance I guess). Now, that's a lot more powerful, but if I'm using something that doesn't even need the 100MB of RAM, I might as well save some money and use Redis to Go.

Plus you get the added bonus of still not having to worry about any piece of your infrastructure.

Redis is dead simple, but having another server isn't. While most people can easily handle this, managing systems can often spin out of control. If you are starting a project would you rather handle another server or just have someone else manage it and be done in under a min?

There are ways to automate server configuration though. AMIs, Chef, Puppet, even Linode's StackScripts.

Reply on news.ycombinator.com