Summary
Geospatial radius query results for static reference points (store locations, service areas) can be cached since the underlying dataset changes infrequently relative to query frequency.
Evidence
- ·geospatial_index lists cache_aside in related_patterns (patterns/geospatial_index.yaml)
- ·cache_aside applicable_when data changes infrequently relative to read frequency (patterns/cache_aside.yaml)
Evidence grounding
Grounded, 2 supporting itemsStatic geo reference points (store locations, service areas) are read-heavy and change rarely, a cache-aside fit.