We could point out the following problem with the Akamai Cache (or CDN Cache) https://madsack.arcpublishing.com/alc/arc-products/arcwide/caching-within-arc/ :
The Akamai-Cache returns a cached html which contains all content-sources.
The content-sources are valid for the moment when this html is created. I think the Akamai-cached-HTML is cached 2 minutes.
When the Akamai-Cached-HTML is delivered the first time to the client all content-sources are valid
Now it is possible that a Content-Source expires whithin the 2 minutes while the Akamai-Cached-HTML is valid
So if a content source expires after e.g. 10 seconds, it is fetched every time in the last 1:50 minutes when the page gets reloaded by the client.
My idea to solve the problem:
When the Akamai-Cache is building the html and is fetching the content sources it should check if the content-sources are expiring within the 2 minutes.
If a content-source expires within the 2 minutes the content-source has to be updatet, so that the content source is valid as long as possible. That means use
api/v3/content/update/ instead of
(If a content-Source has a time to live which is lower than the 2 minutes it gets at least fetched as seldom as possible)
Is it possible to change the Akamai Cache in this way?