<?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 (jm)</title>
    <link>https://pinboard.in/u:jm/public/</link>
    <description>recent bookmarks from jm</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://gist.github.com/acolyer/95ef23802803cb8b4eb5"/>
	<rdf:li rdf:resource="http://www.slideshare.net/AmazonWebServices/cpn208-failuresatscale-aws-reinvent-2012"/>
	<rdf:li rdf:resource="http://perspectives.mvdirona.com/2012/02/11/PerspectivesOnTheCostaConcordiaIncident.aspx"/>
	<rdf:li rdf:resource="http://perspectives.mvdirona.com/2011/10/01/ChangesInNetworkingSystems.aspx"/>
	<rdf:li rdf:resource="http://perspectives.mvdirona.com/2011/03/26/PrioritizingPrinciplasInOnDesigningAndDeployingInternetScaleServices.aspx"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://gist.github.com/acolyer/95ef23802803cb8b4eb5">
    <title>Internet Scale Services Checklist</title>
    <dc:date>2015-04-21T11:39:07+00:00</dc:date>
    <link>https://gist.github.com/acolyer/95ef23802803cb8b4eb5</link>
    <dc:creator>jm</dc:creator><description><![CDATA[good aspirational checklist, inspired heavily by James Hamilton's seminal 2007 paper, "On Designing And Deploying Internet-Scale Services"]]></description>
<dc:subject>james-hamilton checklists ops internet-scale architecture operability monitoring reliability availability uptime aspirations</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:827aeebe6695/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:james-hamilton"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:checklists"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:internet-scale"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:operability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:monitoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:reliability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:availability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:uptime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aspirations"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.slideshare.net/AmazonWebServices/cpn208-failuresatscale-aws-reinvent-2012">
    <title>James Hamilton - Failures at Scale &amp; How to Ride Through Them - AWS re:Invent 2012 - Cpn208</title>
    <dc:date>2012-12-02T00:23:58+00:00</dc:date>
    <link>http://www.slideshare.net/AmazonWebServices/cpn208-failuresatscale-aws-reinvent-2012</link>
    <dc:creator>jm</dc:creator><description><![CDATA[mostly an update of his classic USENIX paper, but pretty cool to come across a mention of a network monitoring system we've built on page 21 ;)]]></description>
<dc:subject>amazon james-hamilton reliabilty slides aws</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:db7ed8f7e60f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:james-hamilton"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:reliabilty"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:slides"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://perspectives.mvdirona.com/2012/02/11/PerspectivesOnTheCostaConcordiaIncident.aspx">
    <title>Perspectives on the Costa Concordia Incident</title>
    <dc:date>2012-02-20T00:02:40+00:00</dc:date>
    <link>http://perspectives.mvdirona.com/2012/02/11/PerspectivesOnTheCostaConcordiaIncident.aspx</link>
    <dc:creator>jm</dc:creator><description><![CDATA[hey, co-worker Rory Browne gets namechecked on James Hamilton's blog!  woo]]></description>
<dc:subject>costa-concordia amazon james-hamilton disaster boats safety post-mortem</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:2da527e6a7e4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:costa-concordia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:james-hamilton"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:disaster"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:boats"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:safety"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:post-mortem"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://perspectives.mvdirona.com/2011/10/01/ChangesInNetworkingSystems.aspx">
    <title>Amazon hiring embedded OS developers</title>
    <dc:date>2011-10-02T22:37:00+00:00</dc:date>
    <link>http://perspectives.mvdirona.com/2011/10/01/ChangesInNetworkingSystems.aspx</link>
    <dc:creator>jm</dc:creator><description><![CDATA[hey, I know a few of those!  'I need more help on a project I’m driving at Amazon where we continue to make big changes in our datacenter network to improve customer experience and drive down costs while, at the same time, deploying more gear into production each day than all of Amazon.com used back in 2000. It’s an exciting time and we have big changes happening in networking. If you enjoy and have experience in operating systems, networking protocol stacks, or embedded systems and you would like to work on one of the biggest networks in the world, [get in touch].' -- James Hamilton]]></description>
<dc:subject>james-hamilton aws jobs amazon networking embedded</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:111378985533/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:james-hamilton"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:jobs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:embedded"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://perspectives.mvdirona.com/2011/03/26/PrioritizingPrinciplasInOnDesigningAndDeployingInternetScaleServices.aspx">
    <title>Brad Porter's top five principles from &quot;On Designing and Deploying Internet-Scale Services&quot;</title>
    <dc:date>2011-03-27T22:47:53+00:00</dc:date>
    <link>http://perspectives.mvdirona.com/2011/03/26/PrioritizingPrinciplasInOnDesigningAndDeployingInternetScaleServices.aspx</link>
    <dc:creator>jm</dc:creator><description><![CDATA[still fantastic advice, even after 4 years.  I think it's time for a re-read]]></description>
<dc:subject>internet software james-hamilton design architecture coding advice services scaling reliability</dc:subject>
<dc:identifier>https://pinboard.in/u:jm/b:aae2778d4b3c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:james-hamilton"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:advice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:services"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:reliability"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>