<?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://instagram-engineering.tumblr.com/post/89992572022/migrating-aws-fb"/>
	<rdf:li rdf:resource="http://yobriefca.se/blog/2013/04/29/micro-service-architecture/"/>
	<rdf:li rdf:resource="http://techblog.netflix.com/2013/03/introducing-first-netflixoss-recipe-rss.html"/>
	<rdf:li rdf:resource="http://graphics.cs.cmu.edu/projects/whatMakesParis/"/>
	<rdf:li rdf:resource="http://cfengine.com/markburgess/blog_cap.html"/>
	<rdf:li rdf:resource="http://highscalability.com/blog/2012/6/29/stuff-the-internet-says-on-scalability-for-june-29-2012-the.html"/>
	<rdf:li rdf:resource="http://www.infoq.com/articles/cap-twelve-years-later-how-the-rules-have-changed"/>
	<rdf:li rdf:resource="http://highscalability.com/blog/2012/3/26/7-years-of-youtube-scalability-lessons-in-30-minutes.html"/>
	<rdf:li rdf:resource="http://www.12factor.net/"/>
	<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://basho.com/blog/technical/2012/03/05/Instantish-Real-Service-Architecture-BashoChats002/"/>
	<rdf:li rdf:resource="http://thinkvitamin.com/code/steve-huffman-on-lessons-learned-at-reddit/"/>
	<rdf:li rdf:resource="http://www.ics.uci.edu/~cs223/papers/cidr07p15.pdf"/>
	<rdf:li rdf:resource="http://www.michaelpiatek.com/papers/thialfi-sosp11.pdf"/>
	<rdf:li rdf:resource="http://research.microsoft.com/en-us/people/aguilera/nomad-atc2011.pdf"/>
	<rdf:li rdf:resource="http://www.nosql.es/blog/wp-content/uploads/2010/04/10.1.1.80.7427.pdf"/>
	<rdf:li rdf:resource="http://matt-welsh.blogspot.com/2010/07/retrospective-on-seda.html"/>
	<rdf:li rdf:resource="http://queue.acm.org/detail.cfm?id=1971597"/>
	<rdf:li rdf:resource="http://www.eecs.harvard.edu/~mdw/papers/seda-sosp01.pdf"/>
	<rdf:li rdf:resource="http://highscalability.com/blog/2011/3/22/facebooks-new-realtime-analytics-system-hbase-to-process-20.html"/>
	<rdf:li rdf:resource="http://www.slideshare.net/danmckinley/etsy-activity-feeds-architecture"/>
	<rdf:li rdf:resource="http://techblog.netflix.com/2011/01/nosql-at-netflix.html"/>
	<rdf:li rdf:resource="http://unreal.epicgames.com/Network.htm"/>
	<rdf:li rdf:resource="http://www.eecs.harvard.edu/~michaelm/postscripts/kdd2009.pdf"/>
	<rdf:li rdf:resource="http://bret.appspot.com/entry/how-friendfeed-uses-mysql"/>
	<rdf:li rdf:resource="http://en.wikipedia.org/wiki/Paxos_algorithm"/>
	<rdf:li rdf:resource="http://www.cs.cornell.edu/projects/ladis2009/talks/dean-keynote-ladis2009.pdf"/>
	<rdf:li rdf:resource="http://www.facebook.com/notes/facebook-engineering/the-full-stack-part-i/461505383919"/>
	<rdf:li rdf:resource="http://highscalability.com/blog/2010/11/16/facebooks-new-real-time-messaging-system-hbase-to-store-135.html"/>
	<rdf:li rdf:resource="http://www.iamcal.com/talks/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://instagram-engineering.tumblr.com/post/89992572022/migrating-aws-fb">
    <title>Migrating From AWS to FB - Instagram Engineering</title>
    <dc:date>2014-06-27T00:38:09+00:00</dc:date>
    <link>http://instagram-engineering.tumblr.com/post/89992572022/migrating-aws-fb</link>
    <dc:creator>mncaudill</dc:creator><dc:subject>instagram architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:4faad8fc8b10/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:instagram"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://yobriefca.se/blog/2013/04/29/micro-service-architecture/">
    <title>Micro Service Architecture</title>
    <dc:date>2013-08-05T04:37:57+00:00</dc:date>
    <link>http://yobriefca.se/blog/2013/04/29/micro-service-architecture/</link>
    <dc:creator>mncaudill</dc:creator><dc:subject>architecture services soa</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:22c36d784e7a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:services"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:soa"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://techblog.netflix.com/2013/03/introducing-first-netflixoss-recipe-rss.html">
    <title>The Netflix Tech Blog: Introducing the first NetflixOSS Recipe: RSS Reader</title>
    <dc:date>2013-03-14T15:38:53+00:00</dc:date>
    <link>http://techblog.netflix.com/2013/03/introducing-first-netflixoss-recipe-rss.html</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA[    While we continue to open source more of our components, it would be useful to open source a set of applications that can tie up these components together.  This is the first in the series of “Netflix OSS recipes” that we intend to open source in the ]]></description>
<dc:subject>netflix architecture rss</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:d5ce41a0ecc9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:netflix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:rss"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://graphics.cs.cmu.edu/projects/whatMakesParis/">
    <title>What Makes Paris Look like Paris?</title>
    <dc:date>2012-08-13T06:33:59+00:00</dc:date>
    <link>http://graphics.cs.cmu.edu/projects/whatMakesParis/</link>
    <dc:creator>mncaudill</dc:creator><dc:subject>architecture flickr googlestreetview paris</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:d7ddd9f86022/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:flickr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:googlestreetview"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:paris"/>
</rdf:Bag></taxo:topics>
</item>
<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/6/29/stuff-the-internet-says-on-scalability-for-june-29-2012-the.html">
    <title>High Scalability - High Scalability - Stuff The Internet Says On Scalability For June 29, 2012 - The Velocity Edition</title>
    <dc:date>2012-06-29T21:36:04+00:00</dc:date>
    <link>http://highscalability.com/blog/2012/6/29/stuff-the-internet-says-on-scalability-for-june-29-2012-the.html</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA[Things I'll want to read.]]></description>
<dc:subject>velocity ops architecture resilience</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:9812fdf184b4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:velocity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:resilience"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.infoq.com/articles/cap-twelve-years-later-how-the-rules-have-changed">
    <title>InfoQ: CAP Twelve Years Later: How the &quot;Rules&quot; Have Changed</title>
    <dc:date>2012-05-30T19:34:28+00:00</dc:date>
    <link>http://www.infoq.com/articles/cap-twelve-years-later-how-the-rules-have-changed</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA[CAP Twelve Years Later: How the "Rules" Have Changed]]></description>
<dc:subject>nosql architecture sql cap</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:6353f8ffb9f1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:nosql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:sql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:cap"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://highscalability.com/blog/2012/3/26/7-years-of-youtube-scalability-lessons-in-30-minutes.html">
    <title>High Scalability - High Scalability - 7 Years of YouTube Scalability Lessons in 30 Minutes</title>
    <dc:date>2012-03-26T18:59:35+00:00</dc:date>
    <link>http://highscalability.com/blog/2012/3/26/7-years-of-youtube-scalability-lessons-in-30-minutes.html</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA["Systems have a tendency to self synchronize as operations line up and try to destroy themselves. Fascinating to watch."]]></description>
<dc:subject>architecture design python scalability</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:5666f7cef0cb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.12factor.net/">
    <title>The Twelve-Factor App</title>
    <dc:date>2012-03-15T00:52:48+00:00</dc:date>
    <link>http://www.12factor.net/</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA[In the modern era, software is commonly delivered as a service: called web apps, or software-as-a-service. ]]></description>
<dc:subject>architecture development</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:8fa97413a621/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:development"/>
</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://basho.com/blog/technical/2012/03/05/Instantish-Real-Service-Architecture-BashoChats002/">
    <title>Basho | Instant-ish Real Service Architecture</title>
    <dc:date>2012-03-08T06:54:17+00:00</dc:date>
    <link>http://basho.com/blog/technical/2012/03/05/Instantish-Real-Service-Architecture-BashoChats002/</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA[There's a whole lot in this that just seems right to me. ]]></description>
<dc:subject>architecture video simple services jvm</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:f4c2d5ad4082/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:simple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:services"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:jvm"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://thinkvitamin.com/code/steve-huffman-on-lessons-learned-at-reddit/">
    <title>Steve Huffman on Lessons Learned at Reddit | Think Vitamin</title>
    <dc:date>2012-02-23T06:16:03+00:00</dc:date>
    <link>http://thinkvitamin.com/code/steve-huffman-on-lessons-learned-at-reddit/</link>
    <dc:creator>mncaudill</dc:creator><dc:subject>architecture performance reddit scaling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:19db447d446c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:reddit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:scaling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.ics.uci.edu/~cs223/papers/cidr07p15.pdf">
    <title>Life beyond Distributed Transactions: an Apostate’s Opinion</title>
    <dc:date>2012-01-16T06:19:54+00:00</dc:date>
    <link>http://www.ics.uci.edu/~cs223/papers/cidr07p15.pdf</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA["The Maginot Line was a huge fortress that ran the length 
of the Franco-German border and was constructed at great 
expense between World War I and World War II.  It 
successfully kept the German army from directly crossing 
the border between France and Germany.  It was quickly 
bypassed by the Germans in 1940 who invaded through 
Belgium"]]></description>
<dc:subject>distributed architecture database sidenote</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:79578f650453/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:sidenote"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.michaelpiatek.com/papers/thialfi-sosp11.pdf">
    <title>Thialﬁ: A Client Notiﬁcation Service for Internet-Scale Applications</title>
    <dc:date>2011-10-04T19:53:46+00:00</dc:date>
    <link>http://www.michaelpiatek.com/papers/thialfi-sosp11.pdf</link>
    <dc:creator>mncaudill</dc:creator><dc:subject>pubsub architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:081b63cfa645/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:pubsub"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://research.microsoft.com/en-us/people/aguilera/nomad-atc2011.pdf">
    <title>research.microsoft.com/en-us/people/aguilera/nomad-atc2011.pdf</title>
    <dc:date>2011-09-07T23:22:21+00:00</dc:date>
    <link>http://research.microsoft.com/en-us/people/aguilera/nomad-atc2011.pdf</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA[We consider the problem of migrating user data between data centers. We introduce distributed storage
overlays, a simple abstraction that represents data as
stacked layers in different places. Overlays can be readily
used to cache data objects, migrate these caches, and migrate the home of data objects. We implement overlays as
part of a key-value object store called Nomad, designed to
span many data centers. Using Nomad, we compare overlays against common migration approaches and show that
overlays are more ﬂexible and impose less overhead. To
drive migration decisions, we propose policies for predicting the location of future accesses, focusing on a web
mail application. We evaluate the migration policies using
real traces of user activity from Hotmail.]]></description>
<dc:subject>storage architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:af74e40c5759/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:storage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nosql.es/blog/wp-content/uploads/2010/04/10.1.1.80.7427.pdf">
    <title>The ϕ Accrual Failure Detector</title>
    <dc:date>2011-05-16T03:09:54+00:00</dc:date>
    <link>http://www.nosql.es/blog/wp-content/uploads/2010/04/10.1.1.80.7427.pdf</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA["Detecting failures is a fundamental issue for fault-tolerance in distributed systems. Recently, many people have
come to realize that failure detection ought to be provided as some form of generic service, similar to IP address
lookup or time synchronization. However, this has not been successful so far. One of the reasons is the difﬁculty
to satisfy several application requirements simultaneously when using classical failure detectors."]]></description>
<dc:subject>faulttolerance distributed architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:ac119a8b18d4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:faulttolerance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://matt-welsh.blogspot.com/2010/07/retrospective-on-seda.html">
    <title>Volatile and Decentralized: A Retrospective on SEDA</title>
    <dc:date>2011-04-30T07:18:39+00:00</dc:date>
    <link>http://matt-welsh.blogspot.com/2010/07/retrospective-on-seda.html</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA["The most important contribution of SEDA, I think, was the fact that we made load and resource bottlenecks explicit in the application programming model."

When your systems are distributed, with varying throughput and resiliency, you can't treat pieces of your architecture as function calls, returning data instantly, consistently, and reliably. The "load and resource bottlenecks" are integral parts of the logic of your software and contracts have to be written and programmed against.]]></description>
<dc:subject>distributed architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:d819bcd6b36e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://queue.acm.org/detail.cfm?id=1971597">
    <title>Scalable SQL - ACM Queue</title>
    <dc:date>2011-04-21T04:15:10+00:00</dc:date>
    <link>http://queue.acm.org/detail.cfm?id=1971597</link>
    <dc:creator>mncaudill</dc:creator><dc:subject>architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:93e6a2319d70/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.eecs.harvard.edu/~mdw/papers/seda-sosp01.pdf">
    <title>www.eecs.harvard.edu/~mdw/papers/seda-sosp01.pdf</title>
    <dc:date>2011-04-07T03:03:32+00:00</dc:date>
    <link>http://www.eecs.harvard.edu/~mdw/papers/seda-sosp01.pdf</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA[SEDA: An Architecture for Well-Conditioned,
Scalable Internet Services]]></description>
<dc:subject>algorithms architecture distributed</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:1e4e0a90b7fb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:algorithms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:distributed"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://highscalability.com/blog/2011/3/22/facebooks-new-realtime-analytics-system-hbase-to-process-20.html">
    <title>High Scalability - High Scalability - Facebook's New Realtime Analytics System: HBase to Process 20 Billion Events Per Day</title>
    <dc:date>2011-03-23T03:03:14+00:00</dc:date>
    <link>http://highscalability.com/blog/2011/3/22/facebooks-new-realtime-analytics-system-hbase-to-process-20.html</link>
    <dc:creator>mncaudill</dc:creator><dc:subject>architecture scaling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:96450b0ff546/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:scaling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.slideshare.net/danmckinley/etsy-activity-feeds-architecture">
    <title>Etsy Activity Feeds Architecture</title>
    <dc:date>2011-03-05T17:45:56+00:00</dc:date>
    <link>http://www.slideshare.net/danmckinley/etsy-activity-feeds-architecture</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA[How Etsy built their activity feed. Mention of how a certain part is a hack and won't scale is interesting...]]></description>
<dc:subject>architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:f47133d580d7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://techblog.netflix.com/2011/01/nosql-at-netflix.html">
    <title>NoSQL at Netflix</title>
    <dc:date>2011-01-28T22:57:02+00:00</dc:date>
    <link>http://techblog.netflix.com/2011/01/nosql-at-netflix.html</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA[A little light on details but talks a bit about how they use Amazon SimpleDB, Cassandra, and HBase.]]></description>
<dc:subject>distributed architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:da16d50da554/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://unreal.epicgames.com/Network.htm">
    <title>Unreal Networking Architecture</title>
    <dc:date>2011-01-09T06:28:52+00:00</dc:date>
    <link>http://unreal.epicgames.com/Network.htm</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA["Multiplayer gaming is about shared reality: that all of the players feel they are in the same world, seeing from differing viewpoints the same events transpiring within that world.  As multiplayer gaming has evolved from the little 2-player modem games that characterized Doom, into the large, persistent, more free-form interactions of games like Quake 2, Unreal, and Ultima Online, the technologies behind the shared reality have evolved tremendously."]]></description>
<dc:subject>architecture games</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mncaudill/b:889196ee15ba/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:games"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.eecs.harvard.edu/~michaelm/postscripts/kdd2009.pdf">
    <title>On Compressing Social Networks</title>
    <dc:date>2010-12-16T16:28:09+00:00</dc:date>
    <link>http://www.eecs.harvard.edu/~michaelm/postscripts/kdd2009.pdf</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA["We show that some of the problems are NP-hard yet admit effective heuristics..." 

Effective heuristics are always good.
]]></description>
<dc:subject>scalability architecture graph</dc:subject>
<dc:identifier>https://pinboard.in/u:mncaudill/b:4a5a14445263/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:graph"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bret.appspot.com/entry/how-friendfeed-uses-mysql">
    <title>How FriendFeed uses MySQL to store schema-less data - Bret ...</title>
    <dc:date>2010-12-07T16:10:28+00:00</dc:date>
    <link>http://bret.appspot.com/entry/how-friendfeed-uses-mysql</link>
    <dc:creator>mncaudill</dc:creator><dc:subject>toread scaling architecture</dc:subject>
<dc:identifier>https://pinboard.in/u:mncaudill/b:bfe88d2ced99/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:toread"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://en.wikipedia.org/wiki/Paxos_algorithm">
    <title>Paxos algorithm - Wikipedia, the free encyclopedia</title>
    <dc:date>2010-12-03T07:40:02+00:00</dc:date>
    <link>http://en.wikipedia.org/wiki/Paxos_algorithm</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA[Paxos is a family of protocols for solving consensus in a network of unreliable processors. Consensus is the process of agreeing on one result among a group of participants. This problem becomes difficult when the participants or their communication medium may experience failures.
]]></description>
<dc:subject>architecture toread cs database algorithms</dc:subject>
<dc:identifier>https://pinboard.in/u:mncaudill/b:02dbf5b8e29d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:toread"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:cs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:algorithms"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cs.cornell.edu/projects/ladis2009/talks/dean-keynote-ladis2009.pdf">
    <title>http://www.cs.cornell.edu/projects/ladis2009/talks/dean-keynote-ladis2009.pdf</title>
    <dc:date>2010-12-03T07:06:57+00:00</dc:date>
    <link>http://www.cs.cornell.edu/projects/ladis2009/talks/dean-keynote-ladis2009.pdf</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA[Just great stuff.
]]></description>
<dc:subject>architecture</dc:subject>
<dc:identifier>https://pinboard.in/u:mncaudill/b:f6361d406b18/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.facebook.com/notes/facebook-engineering/the-full-stack-part-i/461505383919">
    <title>Facebook | The Full Stack, Part I</title>
    <dc:date>2010-12-03T06:30:28+00:00</dc:date>
    <link>http://www.facebook.com/notes/facebook-engineering/the-full-stack-part-i/461505383919</link>
    <dc:creator>mncaudill</dc:creator><dc:subject>architecture cs database</dc:subject>
<dc:identifier>https://pinboard.in/u:mncaudill/b:93d0b07b680f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:cs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:database"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://highscalability.com/blog/2010/11/16/facebooks-new-real-time-messaging-system-hbase-to-store-135.html">
    <title>High Scalability - High Scalability - Facebook's New Real-time Messaging System: HBase to Store 135+ Billion Messages a Month</title>
    <dc:date>2010-11-16T22:29:29+00:00</dc:date>
    <link>http://highscalability.com/blog/2010/11/16/facebooks-new-real-time-messaging-system-hbase-to-store-135.html</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA[Facebook also has an extensive MySQL infrastructure, but they found performance suffered as data set and indexes grew larger. And they could have built their own, but they chose HBase.
]]></description>
<dc:subject>database scalability architecture</dc:subject>
<dc:identifier>https://pinboard.in/u:mncaudill/b:85d36995ae87/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.iamcal.com/talks/">
    <title>Talks [ on iamcal.com ]</title>
    <dc:date>2009-04-30T17:11:22+00:00</dc:date>
    <link>http://www.iamcal.com/talks/</link>
    <dc:creator>mncaudill</dc:creator><description><![CDATA[Speaking respository of a former flickr engineer, Cal Henderson. Lots of information about PHP and scaling, obviously.
]]></description>
<dc:subject>flickr scalability architecture php webdev</dc:subject>
<dc:identifier>https://pinboard.in/u:mncaudill/b:da5a3edbc9bf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:flickr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mncaudill/t:webdev"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>