#cache-for-redis

Azure Cache for Redis: Stale Reads from Secondary Replica After Write

Problem Statement Applications that write to a primary Azure Cache for Redis instance and subsequently read from a secondary replica for read‑scaling can observe stale values because replication is asynchronous. The replication lag can range from milliseconds to seconds, and there is no built‑in mechanism to redirect reads back to the primary immediately aft

Microsoft Azure · Editorial question

geo-replicationazurecache-for-redis