After the first hit to the page in aem and HTML response received for first time from publish instance will get cached on Akamai level. Subsequent request to the same page will be served from the cached content in Akamai rather than hitting dispatcher / publisher. Anytime did you struggled to get the latest HTML from publisher instead of Akamai cache? Well we did!!! What we have donePermalink We have worked on AEM replication agent for flushing Akamai cache whenever page gets published. So, after author change a page content and publish it our Akamai cache flush agent will pick that page and request to akamai for clearing cache. So that user of that page will get the latest content instead of cached old content from Akamai. It is all automated, we don’t need to clear the Akamai cache when new product goes live to prod. We don’t ask DevOps to clear Akamai cache so customers will see latest page. Lets save their 1-2 mins time whenever new product launch.
Please use this thread to ask the related questions.
Topics help categorize Community content and increase your ability to discover relevant content.