<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (mncaudill)</title>
    <link>https://pinboard.in/u:mncaudill/public/</link>
    <description>recent bookmarks from mncaudill</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://cfengine.com/markburgess/blog_cap.html"/>
	<rdf:li rdf:resource="http://highscalability.com/blog/2012/3/12/google-taming-the-long-latency-tail-when-more-machines-equal.html"/>
	<rdf:li rdf:resource="http://www.sfgate.com/cgi-bin/article.cgi?f=/c/a/2011/04/20/BANM1J3LL1.DTL"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://cfengine.com/markburgess/blog_cap.html">
    <title>Deconstructing the `CAP theorem' for CM and DevOps</title>
    <dc:date>2012-08-09T16:22:07+00:00</dc:date>
    <link>http://cfengine.com/markburgess/blog_cap.html</link>
    <dc:creator>mncaudill</dc:creator><dc:subject>devops cap architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:37154b2b0b20/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:devops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:cap"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://highscalability.com/blog/2012/3/12/google-taming-the-long-latency-tail-when-more-machines-equal.html">
    <title>High Scalability - High Scalability - Google: Taming the Long Latency Tail - When More Machines Equals Worse Results</title>
    <dc:date>2012-03-12T20:21:12+00:00</dc:date>
    <link>http://highscalability.com/blog/2012/3/12/google-taming-the-long-latency-tail-when-more-machines-equal.html</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA["The implication: high performance equals high tolerances, which means your entire system must be designed to exacting standards."]]></description>
<dc:subject>devops google performance architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:61185540b9af/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:devops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.sfgate.com/cgi-bin/article.cgi?f=/c/a/2011/04/20/BANM1J3LL1.DTL">
    <title>SF emergency unit's computer crashed during fire</title>
    <dc:date>2011-04-20T19:30:19+00:00</dc:date>
    <link>http://www.sfgate.com/cgi-bin/article.cgi?f=/c/a/2011/04/20/BANM1J3LL1.DTL</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA[They tried to switch to the backup system but no one knew the password. Painfully obvious that their disaster recovery wasn't automated or at least drilled.]]></description>
<dc:subject>devops disaster fire</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:846bf4a392da/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:devops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:disaster"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:fire"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>