Our on-device product cache key ends in v3, because a field that is absent reads as an answer
DEV Community
Our on-device product cache key ends in v3, because a field that is absent reads as an answer
Three read tiers in front of one endpoint, 24 entries, a one hour bound, and a version suffix that exists because an old cache entry rehydrating with a missing field once made the app lie to people and then write their correction into the database.
0 comments
No comments yet.