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

1

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.

But I doubt whether the network latency I would have in my searches when querying through a connection to a machine that is outside my cluster would be too damaging to my performance, to the point that it would be more feasible to have a machine within my VPC, to use Redis.

Does anyone know how big the performance gap between I / O sent over open network vs. I / O directly on the local disk or in one inside a machine of my private network within the same region on Amazon?

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

    
asked by anonymous 18.10.2016 / 15:19

1 answer

1

At first the disk is always faster than the network, even more so 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 host memory location ...

    
18.10.2016 / 19:43