222 Content Delivery Networks The answers to the previous questions can help the intended audience understand the benefit of using CDN over any other cache technology. “Akamaizing Content” In the way the term xeroxing became a synonym for photocopying, the term akamaizing has become a synonym for automatically rewriting content so it’s CDN-aware. Typically, web sites go through a manual akamaization process where they convert all their existing content, so it becomes CDN-aware. These web sites must also update their web applications, so the applications generate CDN-aware HTML code, and the production of new HTML must undergo an additional step of being made CDN-aware. When all is said and done, the process of making content CDN-aware can be a time-consuming one, despite the automation tools offered by companies like Akamai and Speedera. To assist with this problem, some reverse proxy caches now offer the capability to rewrite content dynamically, so it becomes CDN-aware without any additional work. The ClickArray Networks (http://www.clickarray.com) Array series sports a feature that allows content to be rewritten for any CDN. The content can then be stored in its internal cache for future delivery. Similar to the ClickArray solution, the CacheFlow Server Accelerator series allows content to be dynamically rewritten; however, this only works for the Akamai network. Both solutions are then able to deliver the rewritten content from their cache, thereby reducing even more load on origin servers. Let’s look at a quick example for www.example.com. Assuming no CDN, a web page might look something like this:

My Vacation

Now, assume the content is rewritten for the Akamai network. The resulting content would look like this:

My Vacation

Speedera, on the other hand, uses a slightly different method of rewriting content. A Speedera-ized site would look like this: