When dispatcher caching is not enough

11 August 2015
Jakub Wadolowski
Frink_Cognifide_2016_HeaderImages_0117
Have you ever wondered how big brands like Facebook, Amazon or Twitter deliver content to worldwide audience? How does it happen that whatever your location is you can browse these websites equally fast?

Technology that stays behind it is nothing extraordinary these days. Many companies use Content Delivery Networks (CDN) to distribute their content all around the globe. Regardless of your business profile you can leverage that technology too. It doesn’t really matter if you’re a big media company that operates basically everywhere and publishes new articles multiple times per hour or a small, highly specialized bookstore that sells products to niche group of enthusiasts. As long as you expose your assets through HTTP you’re ready to go!

But how does it apply to Adobe Experience Manager? As you can expect the answers is completely affirmative. The problem, though, is that most probably your AEM stack is no longer just a CMS. It’s a part of a much wider picture. Analytics, external authentication endpoints, search engines or 3rd-party APIs - all these moving parts affect the way your website is served.

Imagine that one of your clients would like to streamline the way they manage marketing content in AEM. One of the crucial points is that majority of aforementioned content will be consumed on iPads. It will be heavily dynamic and available for logged in users only. Moreover your client operates in 180+ countries and definitely don’t want to spend too much on infrastructure and maintenance overhead it may introduce. 

If you’ve ever faced these kind of challenges you should definitely see my talk at AEMHub in London this year! You will see not only how bumpy the road to CDN was, but also:
  • how to authorize your users at the edge?
  • what kind of improvement you might expect?
  • is is really sane to put CDN in front of AEM authoring?
  • and finally, a live demo on stage!