Google Bucket Asset Caching Change Policy

As a developer, you wield the power to dictate how assets are cached. Although media resources are automatically cached, there may be occasions where you need to change the cache-control header. It's crucial to adhere to these policies if you intend to override the default cache settings.

⁠

To alter the cache behavior of a Google Bucket asset, refer to the instructions provided in this documentation.⁠

⁠

UNDERSTAND the implications of modifying the cache-control header

Seek to understand: Always make sure you understand the impact of a cache-control change. If caching mechanisms are unclear or you're unsure about the benefits of cache adjustments for your project, see

@Michael Waskiewicz⁠

for assistance.

Be careful: Always evaluate the potential risk when changing the cache-control. For example, introducing max-age=0 to the cache-control header effectively disables caching for a designated resource. This seemingly innocuous tweak could potentially trigger adverse financial repercussions for the company, particularly for resources that get high traffic volumes. The resulting surge might inflate operational costs unnecessarily.

PROCEED WITH CAUTION when adjusting the max-age parameter in the cache-control header. Consider the following:

Update Frequency: Evaluate how frequently the resource undergoes modifications or updates. Resources that are subject to frequent updates demand a more nuanced caching strategy to ensure that users consistently access the most recent version of the content. Follow the recommendation below for frequently updated assets.

Reasonable Wait Time: Determine what constitutes a reasonable wait time for newly deployed software or updated resources. Balancing the need for timely access with the efficiency of caching mechanisms is paramount in optimizing user experience and resource utilization.

OUR RECOMMENDATION for frequently updated assets:

If you must adjust the cache control header, for libraries or resources that undergo frequent updates, it's recommended to set the cache-control header to max-age=3600. This configuration limits the frequency of fetching these assets from the bucket into Fastly, ensuring that they are refreshed no more than 24 times within a 24-hour period. By striking this delicate balance, you can mitigate excessive server load while ensuring that users consistently access the latest iterations of your resource.

Fastly caching is already enabled for your media assets in the Google Bucket. No need to configure anything!

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.