Last Mile Redis

Summary

Last Mile Redis presents a globally distributed caching design aimed at keeping backend responses under the 100-millisecond threshold by placing Redis near users. It argues that regional datasets overlap less than expected, making one Redis server per region a practical alternative to centralized sharding. The design combines standalone regional caches with a Dallas primary Redis and writable replicas configured with replica-read-only no, allowing local writes while replication distributes global changes. A DEL issued at the primary can therefore purge bad cache data across regions, while timestamped keys and expiration handle ordinary freshness; the same mechanism can also broadcast content or fan out queue messages.

Takeaways

1. 1

   Geographic cache locality means regional datasets often have limited overlap, so one Redis instance per region can avoid explicit application sharding.

2. 2

   Setting replica-read-only no lets regional Redis replicas accept local writes while continuing to sync changes from a primary.

3. 3

   Deleting a bad key on the primary propagates through replicas for an “instant” global purge; the design also supports global SET values and list-based fan-out with LPUSH and BRPOP.