Web page caching gets tricky once personalization is involved. Lets take twitter public_timeline for example which seems to be perfect for caching. Unfortunately when a user is logged in, it also shows the userâ€™s information. Caching that particular page in its entirety, on the web server, in such scenarios, may not be an option. Another scenario is where parts of a page might expire faster than other (require different cache TTLs). Here again caching the whole page doesnâ€™t help.
Edge side includes(ESI) is a markup language specifically designed to help web servers assemble dynamic content at the web layer.
The above ESI tag is similar to tags in jsp/php/etc which allow one page to refer to another page for parts of the content on the page. By breaking up the page into smaller objects the webserver could apply different TTL settings (and user validation) to different parts of content. Twitter used to (and may still ) use â€œVarnishâ€ which supports a subset of ESI specification out of the box.
But caching on the webserver may not be the real reason why this language was invented. ESI is also supported by AkamaiÂ (CDN) on its edge caching product.Â By allowing Akamai edge nodes to do the assembling close to the user, they significantly improve perceived end user performance without giving up personalization or content freshness requirements.