Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM 6.5.6 | How is AEM stiching the page?

Avatar

Level 2

When we create AEM editable templates and components as drag and drop , how does the AEM stitch the page on user-end/ browser ?  Is it called as an HTML page ? or each component and their content are separately called and stitched together in browser.

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

6.5
1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Annie_Rose_Peter 

 

      This is a vast topic. I have tried to explain the Sling Resolution in one of my articles. Might be helpful. Please check https://www.linkedin.com/pulse/sling-resource-resolution-aem-part-1-veena-vikraman/ https://www.linkedin.com/pulse/sling-resource-resolution-aem-part-2-veena-vikraman/ 

 

Thanks

Veena

View solution in original post

0 Replies

Avatar

Community Advisor

Hi Annie,

 

This is very broad question. Can you narrow down a bit? Which part of the stitching of AEM are you interested in?

 

Regards,

Peter

 

Avatar

Level 2
Thanks Peter. The reason was load time of static templates were lower than dynamic editable templates . So was checking if the stiching is any diffrent in both type templeates

Avatar

Community Advisor

Hi @Annie_Rose_Peter 

 

When we create a page(HTML) in AEM from a template and add component on it by authoring different content the whole page is considered as an HTML page.

Now When the request is made to the perticular page from browser side, the call is made to the server where the HTML page is rendered by calling the components on it. Now each of the component will have their own HTL (HTML templating Language) which will be executed at the server side and it will generate the content in the form of HTML.

Same HTML content is served to the browser here by caching the content at the dispatcher (caching and load balancing). If the same page request is made in future again the page will be served from the cache to reduce the load on the publish instance. Now there are some other considerations as well like if the content is going to be static or dynamic. If it;s going to be a static content the whole page will be cached whereas if the content is going to be dynamic content the content will be served from the publish instance.

 

Thanks!

Avatar

Correct answer by
Community Advisor

Hi @Annie_Rose_Peter 

 

      This is a vast topic. I have tried to explain the Sling Resolution in one of my articles. Might be helpful. Please check https://www.linkedin.com/pulse/sling-resource-resolution-aem-part-1-veena-vikraman/ https://www.linkedin.com/pulse/sling-resource-resolution-aem-part-2-veena-vikraman/ 

 

Thanks

Veena

Avatar

Level 2

Thanks Veena , that was helpful . The reason why i started looking into these are because a facing an issue where load time of static templates were lower than dynamic media editable templates . Is there any other factors affecting this because as you have mentioned sling will resolve according to the JCR node structure , which will be similar in both cases .

Avatar

Community Advisor
Happy that it helped @Annie_Rose_Peter are you referring to the Dynamic Media for Assets ? Since you Could you edit your question with those details so that someone with more expertise in Dynamic Media can help you with your query .