We are a long-time customer of Fastly and have been using CDN Services in front of our website for many years. Recently I have been working with Fastly tech support and after many weeks of investigations, concluded the following with regards to the Fastly Magento 2 extension:
-
Updating a single product in Magento whilst the standard cron Magento task is running will cause the entire Fastly cache to be purged (shield and POP’s)
-
Running ANY reindexing process in Magento will cause the entire Fastly cache to be purged (shield and POP’s)
Subsequently I can only conclude that the Fastly Magento extension is not compatible with the standard Magento 2 cron background processes, nor is it compatible with standard reindexing requirements of Magento 2 operations (https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/cli/configure-cron-jobs). Disabling all Magento 2 background processes appears to be the only way to maintain an effective caching strategy for a Magento website using Fastly.
I would be interested to hear if there are any other users in the community using the Magento 2 extension and whether they have found a way to keep their site warm whilst running standard Magento cron tasks.