Does Apigee block when doing cache operations?

[#1]

Hello All,

When doing cache operations, are other processes using a given cachekey blocked whilst these operations are occurring on it, or will it perform a dirty read and return the value for a given cachekey until the event is completed?

We're looking at scenario where we would be removing/replacing an existing cachekey... so if we have 10 processes, and process #1 removes and replaces a cachekey, what is the behavior for the other 9 processes that would follow? Would processes #2-#10 go into a wait/blocked state until cache operations are completed from process #1, or will processes #2-#10 get served up a stale cachekey until process #1 completes in its entirety?

Thanks in advance,

Steve

[gnanasekaran · Accepted solution]

Hi @Stephan.Cossette,

Short answer is - it does not block, more details on caching here .

[gnanasekaran · Accepted solution]

Hi @Stephan.Cossette,

Short answer is - it does not block, more details on caching here .

[#4]

Hello Mukundha,

Thanks for the quick response. I didn't think it did either, but wanted to confirm.

Thanks!

Steve

[#5 · Accepted solution]

The model is an eventual consistency model so no blocking occurs. This does mean you could serve for a small window a stale cache entry or in the case of deleting cached entries you may have a slight lag until the entry is removed from all nodes. In my experience on very high volumes your lag my be up to 400 ms. There is no "SLA" per se, just an observation.