We overcome habraeffekt by means of Coral CDN

You put a hyperlink to an interesting site on Habrahabr, and he soon collapses under the influx of visitors, begins to slow down or stop responding altogether.

You put an illustration from another site on your blog, but it soon does not withstand the onslaught of the viewers, ceases to be displayed or is replaced by an ugly notification of excess traffic volumes allocated to it.

These are the unpleasant manifestations of habraeffect - natural DDoS, the analogue of which in the Western West is the slashdot effect.
')
Well, how to resist the natural DDoS?

The most ingenious ways come to mind first.

You can save the image to your disk and then manually upload it to a more stable hosting (and not Radikal.Ru and not ImageShack.US, which turned out to be unusable ), then use the new address of the image.

The whole site to protect from habraeffekt much harder. You can, of course, give a link to the Google cache (or to the Peeep cast , which organized the snusmumrik ), but only the HTML code of the page is stored there, and its illustrations can continue to fall off due to habraeffect.

In addition, all these primitive methods are too distracting. You have to open new tabs, you have to copy the information there and from there. Isn't there a way to allow, without going anywhere, right in the HTML code of your blog entry to indicate the need to protect some URL from habraeffekt?

Yes, this method exists.

It is enough to add the suffix ".nyud.net" to the domain name of the resource. For example, instead of the address of the image “ http://oduinn.com/images/2010/blog_fennec_ff36_cake.jpg ” enter the address “ http://oduinn.com.nyud.net/images/2010/blog_fennec_ff36_cake.jpg ”, and instead of the address of the page “ Http://newtimes.ru/articles/detail.php?ID=14721 ” enter the address “ http://newtimes.ru.nyud.net/articles/detail.php?ID=14721 ”, and so on.

Thanks to this trick, a copy of the resource falls into that CDN (content distribution network), which is called Coral CDN. You can read about Coral CDN either on Wikipedia or on the Coral CDN website - whichever you prefer.

Like torrent file sharing, Coral CDN is open source software (with freely available source code) and uses DHT (distributed hash tables) to transfer files between its nodes. However, the Coral CDN hash table is special: all the algorithms and topology of the Coral CDN are specifically designed so that the network avoids all its nodes being overloaded when it issues the desired files to the reader. Nodes are united for this in "concentric" clusters, each of which only by necessity communicates with higher nodes, and thus saves them from overloading.

In addition to overcoming the habra effect, Coral CDN can be used to bypass the "black lists" of censorship stitched in the DNS, or to open a website bypassing a buggy, inoperable DNS server, if not lucky with the provider. Also, with the help of Coral CDN, you can check illustrations from those sites where you suspect the current prohibition of direct links (hotlinking), because in the Coral CDN such a site will give, of course, not the desired picture, but a graphic notification of the ban.

On Habrahabr Coral CDN can also be used to view comments to the blog recording, which does not unscrew the list of unread comments. If, for example, you want to read all the comments comfortably and at home, but ahead of time to take a look (in a hurry and not completely) from a mobile phone, then look through the Coral CDN.

There is a Coral CDN and restrictions on the size of files and their retention period. Technical details are provided in the local wiki . There's even a recipe for screwing Corel CDN to your site.