<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/user/kasi77/marks/tag/load">
<title>Public marks from user kasi77 with tag load</title>
<description>Public marks from user kasi77 with tag load</description>
<link>http://blogmarks.net/user/kasi77/marks/tag/load</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/1058261427"/>
<rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/1058158657"/>
<rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/1057776198"/>
<rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/1057731864"/>
<rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/1205559"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/kasi77/mark/1058261427">
<title>10 historical software bugs with extreme consequences | Royal Pingdom</title>
<link>http://royal.pingdom.com/2009/03/19/10-historical-software-bugs-with-extreme-consequences/</link>
<description>One of the latest software errors that had widely noticed consequences was Google’s Gmail outage in February. The problem in that case was, according to Google, a bug in the software that distributed load between its different data centers.

The Gmail outage only resulted in people not having access to their email for a few hours. No one got killed. Nothing exploded. It was an inconvenience, and while it was a significant inconvenience for some of Gmail’s users, it was still just that: an inconvenience.

This article is about some of the more dire consequences of software errors through the years. Incidents that make the Gmail outage seem rather trivial.</description>
<dc:date>2009-04-05T19:11:18Z</dc:date>
<dc:author>kasi77</dc:author>
<dc:subject>software, load, email, gmail, it, bug</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://royal.pingdom.com/2009/03/19/10-historical-software-bugs-with-extreme-consequences/"><img border="0" src="http://blogmarks.net/screenshots/2009/04/05/ce0e604ac851c7e71feaf1730e58a26c.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://royal.pingdom.com/2009/03/19/10-historical-software-bugs-with-extreme-consequences/">10 historical software bugs with extreme consequences | Royal Pingdom</a></h4>
 
by <a href="http://blogmarks.net/user/kasi77">kasi77</a> 
<p class="description">One of the latest software errors that had widely noticed consequences was Google’s Gmail outage in February. The problem in that case was, according to Google, a bug in the software that distributed load between its different data centers.

The Gmail outage only resulted in people not having access to their email for a few hours. No one got killed. Nothing exploded. It was an inconvenience, and while it was a significant inconvenience for some of Gmail’s users, it was still just that: an inconvenience.

This article is about some of the more dire consequences of software errors through the years. Incidents that make the Gmail outage seem rather trivial.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/software">software</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/load">load</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/email">email</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gmail">gmail</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/it">it</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bug">bug</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058261427">Copy</a> | 
<a href="http://blogmarks.net/link/3144363">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/kasi77/mark/1058158657">
<title>Royal Pingdom » Why CDNs are great for the Internet, and it’s not for the reason you think</title>
<link>http://royal.pingdom.com/2009/01/12/why-cdns-are-great-for-the-internet-and-its-not-for-the-reason-you-think/</link>
<description>CDNs (Content Delivery Networks) are becoming increasingly popular. The obvious benefit is that they can help websites to give end users a speedier web surfing experience, but there is also another very positive side effect for the entire Internet, and it will become more noticeable the more common CDNs become.

The positive side effect is this: More CDN usage means less load on the Internet backbone.</description>
<dc:date>2009-01-13T13:31:45Z</dc:date>
<dc:author>kasi77</dc:author>
<dc:subject>web, internet, load</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://royal.pingdom.com/2009/01/12/why-cdns-are-great-for-the-internet-and-its-not-for-the-reason-you-think/"><img border="0" src="http://blogmarks.net/screenshots/2009/01/13/768f8292a5ebc984ffe022042d51b2ac.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://royal.pingdom.com/2009/01/12/why-cdns-are-great-for-the-internet-and-its-not-for-the-reason-you-think/">Royal Pingdom » Why CDNs are great for the Internet, and it’s not for the reason you think</a></h4>
 
by <a href="http://blogmarks.net/user/kasi77">kasi77</a> 
<p class="description">CDNs (Content Delivery Networks) are becoming increasingly popular. The obvious benefit is that they can help websites to give end users a speedier web surfing experience, but there is also another very positive side effect for the entire Internet, and it will become more noticeable the more common CDNs become.

The positive side effect is this: More CDN usage means less load on the Internet backbone.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/internet">internet</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/load">load</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058158657">Copy</a> | 
<a href="http://blogmarks.net/link/3056321">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/kasi77/mark/1057776198">
<title>Pingdom Tools</title>
<link>http://tools.pingdom.com/fpt/</link>
<description>The Full Page Test loads a complete HTML page including all objects (images, CSS, JavaScripts, RSS, Flash and frames/iframes). It mimics the way a page is loaded in a web browser.</description>
<dc:date>2008-04-06T17:35:54Z</dc:date>
<dc:author>kasi77</dc:author>
<dc:subject>tools, html, load, test</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://tools.pingdom.com/fpt/"><img border="0" src="http://blogmarks.net/screenshots/2009/04/29/c4c0ce865bea135c2452cb77fa7ef649.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://tools.pingdom.com/fpt/">Pingdom Tools</a></h4>
 
by <a href="http://blogmarks.net/user/kasi77">kasi77</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2306577">12 other(s)</a> 
<p class="description">The Full Page Test loads a complete HTML page including all objects (images, CSS, JavaScripts, RSS, Flash and frames/iframes). It mimics the way a page is loaded in a web browser.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tools">tools</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html">html</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/load">load</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/test">test</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057776198">Copy</a> | 
<a href="http://blogmarks.net/link/2306577">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/kasi77/mark/1057731864">
<title>Comment bien gérer la montée en charge d’une application web ?</title>
<link>http://www.simpleentrepreneur.com/2008/03/11/comment-gerer-la-montee-en-charge-d-une-application-web/</link>
<description>Certaines personnes pensent qu’il ne faut pas trop se focaliser sur les problèmes de montée en charge lorsqu’on démarre le développement d’un nouveau service Internet. A quelques exceptions près (comme par exemple un site de partage de vidéos), il n’est peut-être pas en effet très judicieux de perdre du temps sur cet aspect très technique sans savoir si le succès sera au rendez-vous : on parle alors d’optimisation prématurée.</description>
<dc:date>2008-03-12T19:07:06Z</dc:date>
<dc:author>kasi77</dc:author>
<dc:subject>load, flickr, montée en charge, slides, web</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.simpleentrepreneur.com/2008/03/11/comment-gerer-la-montee-en-charge-d-une-application-web/"><img border="0" src="http://blogmarks.net/screenshots/2008/03/13/3acdb574d4ab2aeb845b44a34e62e736.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.simpleentrepreneur.com/2008/03/11/comment-gerer-la-montee-en-charge-d-une-application-web/">Comment bien gérer la montée en charge d’une application web ?</a></h4>
 
by <a href="http://blogmarks.net/user/kasi77">kasi77</a> 
<p class="description">Certaines personnes pensent qu’il ne faut pas trop se focaliser sur les problèmes de montée en charge lorsqu’on démarre le développement d’un nouveau service Internet. A quelques exceptions près (comme par exemple un site de partage de vidéos), il n’est peut-être pas en effet très judicieux de perdre du temps sur cet aspect très technique sans savoir si le succès sera au rendez-vous : on parle alors d’optimisation prématurée.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/load">load</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/flickr">flickr</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mont%25C3%25A9e%2Ben%2Bcharge">montée en charge</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/slides">slides</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057731864">Copy</a> | 
<a href="http://blogmarks.net/link/2700508">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/kasi77/mark/1205559">
<title>Comment ça marche : la haute disponibilité web - Web Interdit</title>
<link>http://www.webinterdit.com/content/index.php/2006/01/19/34-comment-ca-marche-la-haute-disponiblite-web</link>
<description>Pour gérer des milliers ou des millions d'utilisateurs, un site web se doit de mettre en place un certain nombre de technologies afin que les visites des utilisateurs soient garanties et agréables. En termes techniques, on parle de redondance et de répartition de charge (load balancing en anglais). L'association de ces deux paramètres permet d'atteindre ce qu'on appelle la haute disponibilité : en gros un service qui ne peut pas tomber en panne et qui peut facilement monter en charge.
</description>
<dc:date>2006-11-11T09:14:14Z</dc:date>
<dc:author>kasi77</dc:author>
<dc:subject>web, site, vulgarisation, haute dispo, load</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.webinterdit.com/content/index.php/2006/01/19/34-comment-ca-marche-la-haute-disponiblite-web"><img border="0" src="http://blogmarks.net/screenshots/2006/11/11/70546366e5fcfd855f53fca82d70c815.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.webinterdit.com/content/index.php/2006/01/19/34-comment-ca-marche-la-haute-disponiblite-web">Comment ça marche : la haute disponibilité web - Web Interdit</a></h4>
 
by <a href="http://blogmarks.net/user/kasi77">kasi77</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1236329">1 other(s)</a> 
<p class="description">Pour gérer des milliers ou des millions d'utilisateurs, un site web se doit de mettre en place un certain nombre de technologies afin que les visites des utilisateurs soient garanties et agréables. En termes techniques, on parle de redondance et de répartition de charge (load balancing en anglais). L'association de ces deux paramètres permet d'atteindre ce qu'on appelle la haute disponibilité : en gros un service qui ne peut pas tomber en panne et qui peut facilement monter en charge.
</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/site">site</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/vulgarisation">vulgarisation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/haute%2Bdispo">haute dispo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/load">load</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1205559">Copy</a> | 
<a href="http://blogmarks.net/link/1236329">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>