Tronkle CDN Launching November 1st 2010

Tronkle web hosting service is really a CDN and it’s a revolutionary one in so many ways. But now Tronkle has decided that it’s time for a traditional CDN. This new service will be marketed as “Tronkle Content Delivery Network (CDN)” while the web hosting service will be marketed as “Tronkle Geo-Distributed Web Hosting”.

But why create a traditional CDN when the web hosting service is already a CDN and even far more advanced than a traditional CDN? Because distributing the entire web hosting platform is more expensive than building a traditional CDN and because when distributing the database to more edges write performance decreases. This may not be a problem for 3 or 5 servers but it may be a problem for tens or hundreds of servers. Sometimes people have to distribute static content that will benefit massively from more servers (locations). In this scenario distributing the entire website to all servers will not be beneficial. For this kind of scenarios Tronkle CDN comes to save the day.

By adding traditional CDN services to its’ portfolio Tronkle begins to provide very powerful and highly customizable solutions that scale very well for all websites regardless of traffic volume or usage scenario. The user will be able to have redundant geo-distributed web hosting and choose how many servers he wants and the locations for these servers that best suit his needs. He will then put the static content on Tronkle CDN: more servers in more locations. This will give the best speed for the entire website for all scenarios.

As an example you can consider having your website in Los Angeles, New York and London. This means that your dynamic data will be very fast on West Coast, East Coast and Europe. You can then put your images, videos, javascript files, flash files and all other static content on Tronkle CDN. That content will be served even faster from an even nearer location in Asia, North America and Europe. In addition to that you will have triple redundancy for your website: if anything fails you still have the other servers to serve your website. And of course you will have triple load balancing for your dynamic content and multiple load balancing for your static content. You can customize it as you wish: choose more servers for the dynamic content and spread the locations more if you have infrequent database writes or choose less servers and bring locations closer to each other if you have frequent database writes. It’s up to you to find the best solution and have these wonderful services speed up your website and files like no other.

Tronkle CDN will offer both “push” and “pull” techniques. For those unfamiliar with these terms “push” means that the file is written (pushed) on all servers when it’s inserted in the system while “pull” means that the file is written on-demand (pulled) on each server and cached. You can see more about these techniques in Tronkle FAQ.

One other feature of Tronkle CDN is that it’s provider independent. Some other networks are built upon a single infrastructure provider. We aim to be on as many networks as possible so that we are as close to the user as possible. We also plan to expand Tronkle fast to as many locations as possible according to demand.

Tronkle CDN is not aimed to be low cost but rather affordable. We do promote honesty and fair pricing. Tronkle prices are printed always on our website and start at $9 in order to make our services affordable for everyone. And the best part is that we currently have a “pre-order promotion”: if you sign-up now for Tronkle CDN you get 20% discount for the entire first year. You don’t have to pay anything now; just sign-up before November 1st – that’s when you pay and the service becomes available. You can switch CDN plans later and you will still benefit from the 20% discount for the entire first year. However this discount is only available for CDN services (not web hosting) and only for people that pre-order a CDN service before November 1st.

Tags: , , ,

Slashdot     Delicious  

Leave a Reply

You must be logged in to post a comment.