Should I move to Amazon ElasticCache (Redis) or not?
As you may have noticed Amazon has announced a new feature for its own
ElasticCache product, which is supporting Redis. Here is the link to the
news.
We currently using one EC2 instance for our Redis (just queuing for now)
and we've decided to use Redis for other upcoming features such as
commenting system, discussion, real-time messaging, real-time user
tracking and analytics, etc.
We don't mind to run more and bigger EC2 instances, but should we invest
in ElasticCache (Redis) and move into it from the beginning now that we
haven't started yet or it's too soon to see the results, benchmarks, and
downside? Or it's even limited in some prospectives compare to having your
own Redis on your own instances?
Update 1:
Let me to be detail of what we are going to do with Redis. Probably using
queuing as we have been doing it by Resque. Not sure if ElasticCache let
us do any Pub/Sub but if it does we would like to do that as well. And of
course listing, sorting, and other operational procedures.
No comments:
Post a Comment