4 ms·
Doesn’t local redis kind of miss the point of using redis in the first place? On the surface, that’s a big chunk of additional complexity for something that cou
by catlifeonmars 2y ago
Doesn’t local redis kind of miss the point of using redis in the first place? On the surface, that’s a big chunk of additional complexity for something that could be done internal to an application. Was this meant to be an incremental step in a larger refactor?
- ing33k 2y agowell, redis manages the replication without fuss. Unless the framework / language one uses supports it out of the box, there is no point in re implementing replication. https://www.erlang.org/docs/17/reference_manual/distributed https://www.erlang.org/docs/17/reference_manual/distributed
- catlifeonmars 2y agoOh so this would effectively serve the same purpose as a centralized cluster.
- ing33k 2y agoYeah with the added advantage of reduced latency. The system I worked on had a CRUD application which was in Django , ultimately the rules was stored in a Redis.. The ad serving application was in golang that connected to this local redis instances that were replicas of the central redis.. https://redis.io/docs/latest/commands/replicaof/ https://redis.io/docs/latest/commands/replicaof/
- btilly 2y agoExactly the same for the one that I did, except that the ad serving was in Python. But golang is probably the better choice.