Redis experience | There is no magic here - Alex Dzyoba

Disclaimer – all of these problems arose from our use case and not because Redis is somewhat flawed. Like any piece of software it requires understanding and research before deployed in any decent production environment. We have a data collecting pipeline with the following requirements: Given our requirements we **started to use Redis cluster from the start**. We chose it over single master/replica because we couldn’t fit our 800M+ keys on a single instance and because Redis cluster provides high availability kinda out of the box (you still need to create the cluster with ``` redis-trib.rb ``` or ``` redis-cli --cluster create ``` ). Also, such beefy nodes are very hard to manage – loading of the dataset would take about an hour, the snapshot would take a long time So, I’ve setup Redis cluster and this time I did it without cross replication because I’ve used Google Cloud instances and because cross replication is very tedious to configure and painful to maintain.