A client using AEM 6.5 on-premise is experiencing an unsustainable repository growth of 100Gb a
day. After investigation, an Architect finds out that the DAM is causing this issue. Each image
uploaded to the DAM triggers the creation of approximately 100 renditions, necessary by business to
consume in different channels and systems. The client also complains about stale content reported
by site visitors happening randomly in pages where article-related components are present.
How should the Architect address these issues?
B
Why go for more cost for the customer as an Architect.
This should also work
Leverage AEM Adaptive Image Servlet, cache image variations in Dispatcher, and reimplement article-related components to use AJAX to load the content