We are in the process of migrating this forum. A new space will be available soon. We are sorry for the inconvenience.

cdn, shared hosting cdn and IP cdn

09-22-2010, 09:56 PM

OVH is preparing an offer of "Cdn", "shared hosting cdn" and its pro version "ip cdn. We need some feedback on the needs of such services.

Here are short detail of these three offers:

1.) The "cdn",
we will offer web interface/ftp access to file all of your "static" files. you can use an OVH URL or create a subdomain for you to use the service, for example, cdn. and point to the cdn. infrastructure a bit like shared hosting but static, except that the infrastructure is positioned geographically closest to the visitor. We'll start with Paris, London, Frankfurt and Amsterdam then New York and then other cities in Europe.

why do the service?
the hosting and the dissemination of images and static content, such as sound or video may be "outsourced" to a infrastructure who can collect 24Gbps of traffic (for starters) and several hundreds of millions of queries per second. In short, instead of calculating how many servers I need, simply drop files onto the cdn and add your site http://cdn./files.flv.

2.) the "shared hosting cdn"
if you have shared hosting in OVH, you will be able to switch your domain name to the shared hosting cdn. To change anything at your site, the change of A record of your site is automatic in the manager. As a result, your site is on the CDN infrastructure as "cdn" but with dynamic pages of your site. You switch to unlimited traffic. More precisely everything that is in the directory / shared hosting cdn your site is running out.

why do the service?
The goal here is to manage large sites with high impact without technical expertise. Finally no more than a simple shared hosting.

3.) the "IP cdn"
You can take an "IP cdn" for your dedicated server. Better than an "IP failover" and "IP loadbalancing": you do not have to change anything on your dedicated server. You configure "IP cdn" with the IP of your server. You can set the server to use it on IP1 and if IP1 is down, automatically the traffic must pass on the IP2. Or you can run 2 or 10 IP in parallel or with failover policy. You can set the load distribution along the directory such as /images/ on IP1 and the rest on IP2. You can also define /cdn/ that will type our cdn. "IP cdn" is a bit like "IP failover" + "IP loadbalancing" but also like "IP firewall" that incorporates protections against synflood attacks of any kind. If you have regular attacks, it is simple: you take "IP cdn" and you send traffic to your server. You change the DNS of your site and suddenly you're protected. Also if you have a site in IPv4, you can activate the same site in ipv6 without changing anything with "IP cdn". Finally, if you want to add https with ssl and have performance in ssl, you can activate the certificate on the https. The cdn infrastructure manages the ssl and returns the unencrypted stream to your server. Your server does not use more cpu to encrypt pages.

interesting thing: we speak of your dedicated servers, but they can be anywhere in the world. If you have a site in Japan and want to accelerate for Europe it is the right plan. Also if you have a site in France and you want to accelerate for Germany or USA it is also a good plan. You do not have to have the site operating at OVH.

My question is twofold:

- Did we leave out anything?
- Does it sound interesting?

-or have you no interest in this kind of service?

Welcome all your feedback ... thanks in advance

All the best,