Ah so you meant read write read not write -> read. Yeah KV will by default cache a read for 60s so t
Ah so you meant read write read not write -> read. Yeah KV will by default cache a read for 60s so the reason it takes that long to see the new data is the fact that it is cached. (You are probably not seeing it cached for a full 60s because low request rate and probably a lower plan tier I assume). At the current moment D1 is strongly consistent so a read -> write -> read will be immediate. Read replicas once they become a thing I would assume are going to be push based so it should in theory show a new write faster.
