Size and cost cached data at the edge, including the replication amplification of pushing hot objects to every location.
Edge caches are not one copy of your data: anything popular enough ends up resident in every location, so the billed footprint is the hot set multiplied by the location count plus a single copy of the long tail. Evictions and purges then convert part of that footprint back into origin fetches you pay for again. Replication amplification is what makes an apparently small dataset expensive across 40+ locations, and it is the reason tiered caching exists — confirm the current per-GB storage and fetch prices with your provider, since edge storage is priced very differently from object storage.
Edge Storage
stored bytes = hot share × dataset × locations + cold remainder; cost = stored × storage price + stored × eviction rate × origin fetch price.
stored bytes = hot share × dataset × locations + cold remainder; cost = stored × storage price + stored × eviction rate × origin fetch price. Edge caches are not one copy of your data: anything popular enough ends up resident in every location, so the billed footprint is the hot set multiplied by the location count plus a single copy of the long tail. Evictions and purges then convert part of that footprint back into origin fetches you pay for again.
Replication amplification is what makes an apparently small dataset expensive across 40+ locations, and it is the reason tiered caching exists — confirm the current per-GB storage and fetch prices with your provider, since edge storage is priced very differently from object storage.
This calculator takes 7 inputs: Cacheable dataset, Share hot enough to sit in every location, Edge locations, Average object size, Edge storage price, Cached data refetched each month, Origin fetch price. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.