Study Notes on Caching, Content Delivery, and Rebranding Processes
Overview of Caching and Content Delivery
Importance of speed in SEO
Types of caching:
Browser Caching: Controlled by the end-user.
CDN (Content Delivery Network) Caching: Managed by the company maintaining the website.
Browser vs. CDN Caching
Browser Caching:
Cache duration: Maintained for 1 hour in the browser.
Process: After 1 hour, a new request is sent to the CDN for the image again.
CDN Caching:
Cache duration: Maintained for 12 hours.
Process: After 12 hours, if content changes (e.g., a new image is added), the CDN updates and caches the new image.
Product Data Page (PDP) Caching Scenario
When visiting a net new PDP:
A call to Algolia retrieves product data and assets.
Display occurs via AEM (Adobe Experience Manager) and is cached on the CDN.
Cache duration affects how quickly updates are visible.
Impact of Rebranding on Caching
Expectation of added assets for new branding affects caching:
Integration processes may take around 4 hours.
Issues can arise when assets are updated during the rebranding process.
Recommendation: If content changes are not visible after 16 hours, investigate possible integration issues.
Strategies to Clear Cache
File Name Versioning:
Recommended: Use a unique file name for new images to avoid caching issues.
Avoid: Using the same file name as it continues to reference the cached version.
Unique Query String Parameter:
Example: Adding a timestamp as a query string (e.g.,
?timestamp=123456).Important: Ensure that URLs remain unique to avoid reference caching issues.
Dispatcher Rules:
Defines which pages/assets refresh.
Controls caching duration:
Regular cache: 1 hour (3600 seconds).
Surrogate cache: 12 hours (43200 seconds).
Additional Caching Layer:
Currently under consideration but not yet implemented.
Potential Risks with Cache Clearing Methods
Changing file names can break links in downstream systems.
Caution on impacts on URLs and dependencies.
Solutions may have implications for product images used in various contexts (e.g., partner portals).
Analogy for Understanding Cache Behavior
Comparison with oven baking:
Opening the oven early releases heat, delaying the cooking process.
Waiting for a completed state ensures efficient updates in user experience.
AEM Authoring Environment
No caching is applied within the AEM environment.
Access product images using the product ID directly in the URL without cache interference.
Recommended Practices and Considerations
Ensure good content delivery towards customers efficiently during rebranding.
Always communicate the status of caching changes to maintain seamless integrations and user experience.
Collaboration recommended among team members to ensure processes improve.
Rebranding Updates and Implications
Continuous updates from the rebranding workstreams affecting product catalogs, marketing collateral, and operations.
New processes aimed at ensuring efficient content loading before regulatory approval:
Transitional product content can be uploaded early before full regulatory approval in many cases, improving marketing timelines.
Regulatory Evaluation Points
Two Key Sections:
Product catalog guidance regarding PDP display.
Marketing collateral regulations.
Transitional Content Guidelines:
Allow blended content to be displayed before regulatory approval, aiding in timely product communication to customers.
Workflow Process Post-Manufacturing Transition
Phases aligned with regulatory guidelines:
Phase One (120 days prior): Enables the loading of transitional content.
Phase Two: Full branding allowed post regulatory approvals for transitioning marketing collateral and product content.
Variations in Content Display Regulations
Differentiated by country: Specific exceptions for sensitive products (e.g., drugs).
Collaborative efforts needed among global teams for seamless operations and integration concerning country-specific guidelines.