Dynamic site acceleration

Dynamic site acceleration (DSA) - also known as whole site acceleration - ^[1] is a group of techniques that make the delivery of dynamic websites more efficient.^[2] Manufacturers of application delivery controllers and content delivery networks (CDNs) use the following techniques to accelerate dynamic sites:

Improved connection management, by multiplexing client connections and HTTP keep-alive
Prefetching of -uncachable- web responses
Dynamic cache control
On the fly compression
Full page caching
Off-loading SSL termination
Response based TTL-assignment (bending)
TCP optimization
Route optimization

Techniques

Better connection management: TCP multiplexing

An edge device -this can be an ADC or a CDN- that is capable of TCP multiplexing, can be placed in between web servers and clients, to offload origin servers and accelerate content delivery.

Normally, each connection between client and server, requires a dedicated process that lives on the origin for the duration of the connection. When clients have a slow connection, this occupies part of the origin server, because the process has to stay alive, while the server is waiting for a complete request. With TCP multiplexing, the situation is different. The device obtains a complete and valid request from the client, before sending this to the origin when the request has fully arrived. This offloads application and database servers, which are slower -and more expensive to use- than ADCs or CDNs.^[3]

Dynamic cache control

HTTP has a built-in system for cache control, using cache control headers such as ETag, "expires" and "last-modified". Many CDNs and ADCs, that claim to have DSA, have replaced this with their own system, calling it dynamic caching or dynamic cache control. This gives them more options to invalidate and bypass the cache than the standard HTTP cache control.

The purpose of dynamic cache control is to increase the cache-hit ratio of a website. The cache-hit ratio is the content served from cache, in relation to the content generated by origin servers.

Due to the dynamic nature of web 2.0 websites, it is difficult to use static web caching. The reason for this is that dynamic websites -per definition- have personalized content for different users and/or regions. For example, mobile users may see different content than desktop users, and registered users may need to see different content than anonymous users. Even among registered users, content may vary widely, for example with social media websites.

Static caching of dynamic user-specific pages, introduces a potential risk of serving irrelevant content and/or 3rd party's personal content to the wrong users, if the identifier allowing the caching system to differentiate content, the URL/GET-request, isn't properly variated by appending user-specific tokens/keys to it.

Dynamic cache control has more options to configure caching, such as cookie-based cache control, that allows you to serve content from cache, based on the presence or lack of certain cookies. A cookie stores the unique identifier-key of a logged-in user on their device, and it's already implemented for authenticating users upon execution of any page that opens a session; in a dynamic caching system, the caches are referred to by URL and additionally the various cookie keys, so it allows you to simply enable serving of default caches to anonymous users and personalized caches to logged-in users (without forcing you to modify your code, to make it append additional user identifiers to the URL, like you have to with a static caching system).

Prefetching responses

If personalized content can not be cached, it might be queued on an edge device. That means, that a device stores a list of possible responses, which are ready to be served. This is different than caching, as a prefetched response is only served once. This can be especially useful for accelerating responses of third party APIs, such as advertisements.

Route optimization methodology

Route optimization, also known as "latency-based routing", optimizes the route of traffic between clients and origin servers, to minimize latency. Route optimization can be done by a DNS provider^[4] or by a CDN^[5]

Route optimization comes down to measuring multiple paths between the client and origin server, and then recording the fastest path. This path can then be used to serve content when a client actually makes a request.

Front end optimization

Front end optimization (FEO) and DSA both describe a group of techniques to improve online content delivery. There are overlaps, such as on-the-fly data compression and improved cache-control. However, the key differences are:

FEO focuses on changing the actual content, where as DSA focuses on improving content delivery without touching content (i.e. DSA has verbatim delivery of content). DSA focuses on optimizing bit delivery across the network, without changing the content. FEO aims to decrease the number of objects required to download websites, and to decrease the total amount of traffic. This can be done by device-aware content serving (e.g. dropping the quality of images), minification, resource consolidation and inlining Because FEO changes the actual traffic, configuration tends to be more difficult, as there is a risk of affecting the user-experience, by serving content that was incorrectly changed.
DSA focuses on decreasing page loading times and offloading web-servers, especially for dynamic sites. FEO focuses primarily on decreasing page loading times and reducing bandwidth. Still, cost-savings on origin servers can also be made by implementing FEO: it decreases page loading times, without rewriting code, consequently saving man-hours that would normally be necessary to optimize code. Also, revenue might increase from lower page loading times

References

This article is issued from Wikipedia - version of the Wednesday, March 30, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.