Caching of personalized content pages in AEM 6.1 | Community
Skip to main content
P
promilag4786340
Level 2
October 16, 2015
Solved

Caching of personalized content pages in AEM 6.1

  • October 16, 2015
  • 2 replies
  • 1004 views

We are on AEM 6.1 and we have personalized content on the home page of our website based on the user profile attributes. Let’s assume million user hits the home page, does that mean that home page will be pulled from cq publisher every time instead of dispatcher. Is there any way to improve the performance?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

Hi,

that depends on the way you are doing personalization. If you personalize the page on the server, you need to handle all of these page requests on the server. if you use the client-side personalization of AEM (using ContenxtHub) you can cache much more requests. Depending on what you personalize you still might have JSON calls to the publish, which can be much more lightweight than rendering a complete page.

kind regards,
Jörg

2 replies

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

Hi,

that depends on the way you are doing personalization. If you personalize the page on the server, you need to handle all of these page requests on the server. if you use the client-side personalization of AEM (using ContenxtHub) you can cache much more requests. Depending on what you personalize you still might have JSON calls to the publish, which can be much more lightweight than rendering a complete page.

kind regards,
Jörg

O
Adobe Employee
ogillAdobe Employee
Adobe Employee
October 16, 2015

The approach should be to make as much of the page as static as possible so it can be cached for better performance, so the page is rendered from Dispatcher rather than going to the publish instance.

For any components in the page that need to be rendered based on the user accessing the page(personalised), then it's best to use asynchronous calls at runtime. These calls could be back to the publish instance or they could be to your CRM system, you could then personalise the page for the specific user or personalise the page based on the segment the user matches(you don't need to know exactly who the person is in this use case)

Regards,

Opkar

Terms & ConditionsAccessibility statement

Loading footer...