Caching at Component level in AEM

Hi @abhi-ecm , 

It is possible through Sling Dynamic Include (SDI) where dispatcher is able to cache the whole page but dynamic components are generated and included with every request. 

Please check the below documentation for more details. 

https://github.com/wttech/Sling-Dynamic-Include

https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/development/set-up-sling-dynamic-include.html?lang=en#development

For what reason do you want to implement cacching? Are these components rendered individually (outside of the context of a page) or do you want to cache the components in a way, that rendering them into the context of a page is faster?

"Sling Dynamic Include" can be used to stop caching of one or more components in the dispatcher.

We need to make some configurations on the AEM side and dispatcher side by providing a sling resource type of any component.

 You can refer to the below link to setup Sling Dynamic Include.

https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/development/set-up-sling-dynamic-include.html?lang=en#development

Hi @abhi-ecm 

If you are going for SDI please refer the below links which provides in detail explanation of how the implementation will be:
https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/development/set-up-sling-dynamic-include.html?lang=en#development
https://sling.apache.org/documentation/bundles/dynamic-includes.html

Please note that if you have a CDN running infront of your ALB/dispatcher, you will need to disable the HTML content caching in the CDN to make sure the request reaches the dispatcher followed by the publisher always. If the HTML content is cached in the CDN, SDI will never be able to send request to dispatcher followed by publish instance.

Hope this helps!
Thanks!