Webinar Monday October 6, 2014

aiScaler software is installed on servers to create private point of presence

(PoPs) – much like a CDN endpoint. They cache and serve content to the users.

DNS Traffic Management handles the routing

between geo nodes.

Private CDN, using Dyn for

DNS and aiScaler as POPs.

Hybrid CDN solution, with

massive cost savings for

customers (CNBC saved

80% on their Akamai bill)

DYN TRAFIC MANAGER

• Pre made solution on these cloud providers

Cloud and On Premise solutions

• Customer locations, data centers, other virtualized hosting

Hybrid CDN

Private CDN

Case studies1. Hybrid CDN

• CNBC.com uses aiScaler and Dyn for their hybrid CDN solution. They saved 80% on their Akamai bill, and reduced their hosting costs by 50% (!)

• “our CDN traffic has seen about 80% reduction as well - complete with 80%

reduction in CDN fees “

Quotes:

• “...it allows you to dramatically reduce the hosting footprint - I expect

we shall slash ours by 50%+”

http://highscalability.com/blog/2009/4/16/serving-250m-quotesday-at-cnbccom-with-aicache.html

Case studies1. Private CDN

Amazon daughter (Woot.com) created a private CDN with aiScaler, instead

of using their own CDN (!)

http://aiscaler.com/wp-content/uploads/2013/12/woot_release.pdf

Quote:"With less than a day's work total, we were able to configure aiScaler for use during Woot-Offs. Our site stays up under the crush, and we've saved quite a bit on hardware purchases and time spent optimizing.”

— Luke Duff Retail manager at Woot.com

What kind of customers are a good fit?

•Hybrid CDN: Customers with their own data-center(s) and excess bandwidth capacity. Do they use all the bandwidth capacity from these datacenters? → if there is unused bandwidth capacity, then suggest Hybrid CDN. These customers can save huge amounts by deploying a hybrid CDN. See CNBC

•Private/Hybrid CDN: Customers that have performance problems during peak traffic. Especially if their origin servers are crashing under the load. aiScaler is specifically good at offloading origin servers and cutting page loading times. Dynamic sites in specific.

•Customers that want more control and customization over their content delivery. (see next slide)

•Specific: mobile customersThe aiScaler can remove mobile subdomains, without implementing a responsive design. It also has mobile site acceleration.See:http://aiscaler.com/solutions/mobile

Selling points vs other CDNs

Redundancy:•High Availability from Dyn`s traffic director – Dyn should know best. aiScaler POPs are peer-aware, so there is always an identical failover available.

•aiScaler fallback modes. In case of origin servers go down, then stale content will be showed. For non cachable content a custom error is shown.

•DDoS attacks: Automatic mitigation, alerting and monitoring.

(Let`s not go over this during this presentation. It’s good to have as a reference download link will follow on last slide)

High Performance

•Amazon daughter — Woot.com- created a private CDN with aiScaler, instead of using their own CDN (!)

•“we were able to shave about 1 sec (about 30%!) off page load times, as reported by Keynote.“ — this is in comparison to the world`s biggest CDN.

•aiScaler makes use of Linux and epoll, resulting in virtually unlimited performance: “I have a sneaking suspicion after putting the product through some stress testing that just of a pair of these can run pretty much any website out there “ — CNBC.com

•Dyn helps to cut page loading times. You should know more about this, than we do, so let's skip this.

Selling points vs other CDNs (for later reference)

Selling points vs other CDNs

Customizations. - Not possible with a “one-size-fits-all-CDN”.

Some examples:

•Real-time monitoring and customizable alerting options. Customer quote: "We now have complete, real-time view of traffic - down to RPS, response time, number of connections, cached responses etc”

•Support for custom plug-ins, to solve highly specific problems with your website that are not covered by any CDN yet. These plugins change caching rules and URL rewrites, based on other input, such as Client IP, Cookies, body content, User Agent, Referrer etc. These plugins are are written on-demand by aiScaler engineers.

•A good example of this plugin feature, is a website with paid content, like a Video-on-demand website. They might want to charge different prices to different geographies and also make sure that logged-in, paying visitors see different content than anonymous users.

•Especially sysadmins with dynamic content, will appreciate many options for customizing their content delivery.

(for later reference)

How to set up a proof of concepts?

•POCs use a current production site as an origin, effectively running parallel to the production environment.

•aiScaler POPs on the cloud (points of presence), can be deployed within minutes, using the marketplace from a cloud provider. POC can be cloud-based – even if user plans on-premise deployment

•On-premise POPs have a 30 day free trial.

•aiScaler provides free support for POC. For details, see the provisioning PDF on the next slide.

Here are two PDFs that can help you out with customers:

aiscaler.com/dyn/battlecard

aiscaler.com/dyn/provisioning

Here you can download this presentation:

aiscaler.com/dyn/6oct2014

Any questions?