On modification: When I make changes to my experience fragment(which renders my header), the changes are reflected in header for all the pages in author environment.
On replication: When I replicate the experience fragment, the changes are reflected to Publisher. But it does not reflect in dispatcher, all the pages reflect old header until I go and delete whole cache folder in my dispatcher. I believe cache invalidation request is not associated with experience fragment unlike content fragment.
I have implemented SDI/SSI in AEM 6.3 sites for my header component. Which resolves this issue but then I am concern about the performance of the site.
Because I believe for every page request dispatcher will render whole page from cache but it will by-pass the header component request(As it is SSI) & header will be rendered from Publisher.(Is this understanding right)
So every time my publisher will be engaged for only header component.
I have one question, if we inject a component via SSI, does it mean that it will be requested from publisher everytime or does it create a intermediate cache somewhere in Apache server to render the component?
I have followed many blogs but nowhere I can get clear answer to this question of mine.