<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: ryan-king</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/ryan-king.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2010-05-29T11:36:00+00:00</updated><author><name>Simon Willison</name></author><entry><title>Quoting Ryan King</title><link href="https://simonwillison.net/2010/May/29/spof/#atom-tag" rel="alternate"/><published>2010-05-29T11:36:00+00:00</published><updated>2010-05-29T11:36:00+00:00</updated><id>https://simonwillison.net/2010/May/29/spof/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://github.com/blog/655-scheduled-maintenance-today-22-00-pst#comment-7708"&gt;&lt;p&gt;The easiest way to have no-downtime upgrades is have an architecture that can tolerate some subset of their processes to be down at any time. De-SPOF and this gets easier (not that de-SPOFing is always trivial).&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://github.com/blog/655-scheduled-maintenance-today-22-00-pst#comment-7708"&gt;Ryan King&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/software-architecture"&gt;software-architecture&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/recovered"&gt;recovered&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/zero-downtime"&gt;zero-downtime&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ryan-king"&gt;ryan-king&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spof"&gt;spof&lt;/a&gt;&lt;/p&gt;



</summary><category term="software-architecture"/><category term="recovered"/><category term="zero-downtime"/><category term="ryan-king"/><category term="spof"/></entry></feed>