Hi Sanket,

The short answer is that you can not cache at the edge if you want logic serverside to render diffrent content to diffrent users on the same url.

To make this happend there are som common techniques.

1) DO NOT cache pages with personalization. Use Origin Cache Controll headers to tell your edge if a page can be cached or not. I think there are API to detect if personalization by Visitor Groups are used on a page in Episerver that you can use. If you use other services to personalize the page (like Episervers other services for personalization) you need to take that into account to and you will soon end up with no caching of html pages.

2) DO cache and serve the same html to all visitors, then use client side techniques like javascript to modify the content of your page. It is a common solution to do A/B testing and personlization for third party services. I think this is the most common solution for high traffic sites with a global audience today where you need to cache html request for performance reasons.

3) Use Edge Computing to run a small script on the edge that decides what content to serve the user. In this scenario you can pretty much do anything like modifying the content directly och modify the request url depending on cookies. I have a hard time to see this work with any server side technique like visitorgroups though.

I'm not sure that Akamai CDN on top of Cloudflare is a good solution from a performance perspective since it will cause an extra hop and more latancy but that is another question. If you have not already done so, discuss options with Episerver. Premium support is included with the DXC service.

/Fredrik