Which method is most efficient for scaling, using a redis a service or redis on disk?

Question

I have a question regarding the best approach to caching data using redis. I would like to use a Redis as a Service as Amazon Elasti Cachi or some other.

However I am in doubt if the network latency that I would have in my searches when consulting through a connection with a machine that is outside of my cluster, would harm my performance too much, to the point of being more viable to have a machine within my VPC, to use Redis.

Can anyone tell me how big the performance gap would be between I/O sent by open network vs I/O directly on the local disk or on one inside a machine of my private network within the same region on Amazon?

In view of the performance gain, is it worth taking responsibility and costs to manage a redis infrastructure? Or it is more feasible and practical to use it as a service?

Answer 1

In principle disco is always faster than network, especially if you have to go through the internet... If the volume of data you intend to use is not too large, there would be no problem in putting Redis on another host within the same network, if the volume is large, the best thing to do is to use it local and "clog" the local host memory...

Answer 2

I use the redis in the same network, but I’ve had problems with the volume trafficked in network with the keys of the redis. This problem I solved used Messagepack to decrease the size of the data (instead of using the value of keys in json). To scale the redis, we use twemProxy in front of 3 redis servers, it distributes the keys between the servers and makes the query also, this decreases the number of hits in each redis.