<?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 (sogrady)</title>
    <link>https://pinboard.in/u:sogrady/public/</link>
    <description>recent bookmarks from sogrady</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://gigaom.com/2010/07/21/twitter-to-build-data-center-to-beach-the-fail-whale/"/>
	<rdf:li rdf:resource="http://engineering.twitter.com/2010/04/introducing-gizzard-framework-for.html"/>
	<rdf:li rdf:resource="http://royal.pingdom.com/2010/06/18/the-software-behind-facebook/"/>
	<rdf:li rdf:resource="http://www.rethinkdb.com/blog/2010/03/high-scalability-sql-and-computational-complexity/"/>
	<rdf:li rdf:resource="http://www.roadtofailure.com/2010/02/15/announcing-the-drawn-to-scale-platform/"/>
	<rdf:li rdf:resource="http://nosql.mypopescu.com/post/407159447/cassandra-twitter-an-interview-with-ryan-king"/>
	<rdf:li rdf:resource="http://pl.atyp.us/wordpress/?p=2713"/>
	<rdf:li rdf:resource="http://www.yafla.com/dforbes/Getting_Real_about_NoSQL_and_the_SQL_Isnt_Scalable_Lie"/>
	<rdf:li rdf:resource="http://tantannoodles.com/toolkit/wordpress-s3/"/>
	<rdf:li rdf:resource="http://groups.google.com/group/unladen-swallow/browse_thread/thread/4edbc406f544643e?pli=1"/>
	<rdf:li rdf:resource="http://www.mongodb.org/display/DOCS/Comparing+Mongo+DB+and+Couch+DB"/>
	<rdf:li rdf:resource="http://jsensarma.com/blog/2009/11/dynamo-a-flawed-architecture-part-i/"/>
	<rdf:li rdf:resource="http://www.anchor.com.au/blog/2009/09/github-designing-success/"/>
	<rdf:li rdf:resource="http://blog.digg.com/?p=966"/>
	<rdf:li rdf:resource="http://googleappengine.blogspot.com/2009/02/back-to-future-for-data-storage.html"/>
	<rdf:li rdf:resource="http://jeremy.zawodny.com/blog/archives/010774.html"/>
	<rdf:li rdf:resource="http://www.25hoursaday.com/weblog/2008/11/03/WindowsAzureFromADevelopersPerspective.aspx"/>
	<rdf:li rdf:resource="http://www.theregister.co.uk/2008/11/03/dziuba_azure/"/>
	<rdf:li rdf:resource="http://roy.gbiv.com/untangled/2008/paper-tigers-and-hidden-dragons"/>
	<rdf:li rdf:resource="http://hadoop.apache.org/hbase/"/>
	<rdf:li rdf:resource="http://www.russellbeattie.com/blog/let-the-microblogs-bloom"/>
	<rdf:li rdf:resource="http://blogs.smugmug.com/don/2008/06/03/skynet-lives-aka-ec2-smugmug/"/>
	<rdf:li rdf:resource="http://blog.twitter.com/2008/05/its-not-rocket-science-but-its-our-work.html"/>
	<rdf:li rdf:resource="http://ma.tt/2008/05/infrastructure-as-competitive-advantage/"/>
	<rdf:li rdf:resource="http://highscalability.com/google-appengine-second-look"/>
	<rdf:li rdf:resource="http://www.techcrunch.com/2008/04/04/source-google-to-launch-bigtable-as-web-service/"/>
	<rdf:li rdf:resource="http://radlab.cs.berkeley.edu/wiki/RAD_Lab"/>
	<rdf:li rdf:resource="http://developer.yahoo.com/blogs/hadoop/2008/02/yahoo-worlds-largest-production-hadoop.html"/>
	<rdf:li rdf:resource="http://googlesystem.blogspot.com/2008/01/google-reveals-more-mapreduce-stats.html"/>
	<rdf:li rdf:resource="http://www.igvita.com/2007/12/28/thrudb-faster-and-cheaper-than-simpledb/"/>
	<rdf:li rdf:resource="http://www.allthingsdistributed.com/2007/12/eventually_consistent.html"/>
	<rdf:li rdf:resource="http://bitworking.org/news/276/On-the-importance-of-being-megadata"/>
	<rdf:li rdf:resource="http://aws.typepad.com/aws/2007/10/amazon-ec2-gets.html"/>
	<rdf:li rdf:resource="http://www.flickr.com/photos/8821087@N07/1432492939/"/>
	<rdf:li rdf:resource="http://patricklogan.blogspot.com/2007/09/amqp-xmpp.html"/>
	<rdf:li rdf:resource="http://highscalability.com/demand-infinitely-scalable-database-seed-amazon-ec2-cloud"/>
	<rdf:li rdf:resource="http://www.sauria.com/blog/2007/08/25/scalability-concurrency/"/>
	<rdf:li rdf:resource="http://dev.gentoo.org/~dberkholz/oscon/filesystem-notes.txt"/>
	<rdf:li rdf:resource="http://cfis.savagexi.com/articles/2007/07/18/making-rails-go-vroom"/>
	<rdf:li rdf:resource="http://funkatron.com/index.php/site/comments/what-matt-mullenweg-doesnt-know-about-php5-and-how-it-hurts-him-and-his-use/"/>
	<rdf:li rdf:resource="http://kylecordes.com/2007/07/12/youtube-scalability/"/>
	<rdf:li rdf:resource="http://www.dehora.net/journal/2007/06/comparative_architecture.html"/>
	<rdf:li rdf:resource="http://blog.leetsoft.com/2007/5/22/the-secret-to-memcached"/>
	<rdf:li rdf:resource="http://www.artima.com/scalazine/articles/steps.html"/>
	<rdf:li rdf:resource="http://www.jsequeira.com/blog/2007/05/09.html#a894"/>
	<rdf:li rdf:resource="http://tomayko.com/weblog/2007/04/13/rails-multiple-connections"/>
	<rdf:li rdf:resource="http://www.loudthinking.com/arc/000608.html"/>
	<rdf:li rdf:resource="http://blog.nanobeepers.com/2007/04/07/infinitely-scalable-framework-with-aws/"/>
	<rdf:li rdf:resource="http://bitworking.org/news/158/ETech-07-Summary-Part-2-MegaData"/>
	<rdf:li rdf:resource="http://joyeur.com/2007/04/03/thinking-about-uptime-numbers-for-the-top-20-websites"/>
	<rdf:li rdf:resource="http://swik.net/User:alex/Alex+Bosworth+-+The+Races/The+New+Black%3F+Twitter.com/zw6l"/>
	<rdf:li rdf:resource="http://joyeur.com/2007/03/10/my-heart-twitters-when-i-see-this-chart"/>
	<rdf:li rdf:resource="http://www.gregwhitescarver.com/blog/2007/02/03/scaling-mysql-thoughts-on-replication-sharding-and-mysql-cluster/"/>
	<rdf:li rdf:resource="http://blogs.zdnet.com/BTL/?p=4308"/>
	<rdf:li rdf:resource="http://blog.amber.org/2006/12/11/the-availability-game/"/>
	<rdf:li rdf:resource="http://www.jonathanboutelle.com/mt/archives/2006/12/scalable_web_ar.html"/>
	<rdf:li rdf:resource="http://feh.holsman.net/articles/2006/06/28/memcached-performance"/>
	<rdf:li rdf:resource="http://lists.danga.com/pipermail/memcached/2006-June/002384.html"/>
	<rdf:li rdf:resource="http://dealnews.com/developers/memcached.html"/>
	<rdf:li rdf:resource="http://blog.topix.net/archives/000045.html"/>
	<rdf:li rdf:resource="http://radar.oreilly.com/archives/2006/05/database_war_stories_8_findory_1.html"/>
	<rdf:li rdf:resource="http://weblog.rubyonrails.com/articles/2006/03/07/2-5-million-requests"/>
	<rdf:li rdf:resource="http://pezra.barelyenough.org/blog/2006/02/dynamic-languages-and-the-jvm/#footnote-link-1-207"/>
	<rdf:li rdf:resource="http://www.tbray.org/ongoing/When/200x/2006/02/02/LAMP-Java-Sun"/>
	<rdf:li rdf:resource="http://feedlounge.com/blog/2006/01/29/update-2006-01-29/"/>
	<rdf:li rdf:resource="http://37signals.com/svn/archives2/dont_scale_99999_uptime_is_for_walmart.php"/>
	<rdf:li rdf:resource="http://blog.flickr.com/flickrblog/2005/10/lamp.html"/>
	<rdf:li rdf:resource="http://feedlounge.com/blog/2005/12/05/state-of-feedlounge/"/>
	<rdf:li rdf:resource="http://acmqueue.com/modules.php?name=Content&amp;pa=showpage&amp;pid=337"/>
	<rdf:li rdf:resource="http://jroller.com/page/bsnyder?entry=postgresql_architecture_discussion"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://gigaom.com/2010/07/21/twitter-to-build-data-center-to-beach-the-fail-whale/">
    <title>Twitter to Build Data Center to Beach the Fail Whale</title>
    <dc:date>2010-07-22T21:04:17+00:00</dc:date>
    <link>http://gigaom.com/2010/07/21/twitter-to-build-data-center-to-beach-the-fail-whale/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[an interesting decision on Twitter's part]]></description>
<dc:subject>datacenter hosting twitter reliability scalability</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:sogrady/b:d0499a8efce5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:datacenter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:hosting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:reliability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://engineering.twitter.com/2010/04/introducing-gizzard-framework-for.html">
    <title>The Twitter Engineering Blog: Introducing Gizzard, a framework for creating distributed datastores</title>
    <dc:date>2010-07-16T21:10:54+00:00</dc:date>
    <link>http://engineering.twitter.com/2010/04/introducing-gizzard-framework-for.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[funny to see Twitter and other Web 2.0 companies using the term middleware]]></description>
<dc:subject>twitter gizzard sharding scalability database distributed framework</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:sogrady/b:685add3a4d72/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:gizzard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:sharding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:framework"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://royal.pingdom.com/2010/06/18/the-software-behind-facebook/">
    <title>Exploring the software behind Facebook, the world’s largest site | Royal Pingdom</title>
    <dc:date>2010-07-16T02:55:23+00:00</dc:date>
    <link>http://royal.pingdom.com/2010/06/18/the-software-behind-facebook/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[what FB uses to power it's site]]></description>
<dc:subject>facebook performance scalability scaling software thrift hadoop scribe varnish hiphop</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:sogrady/b:9607060139ad/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:thrift"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scribe"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:varnish"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:hiphop"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.rethinkdb.com/blog/2010/03/high-scalability-sql-and-computational-complexity/">
    <title>[untitled]</title>
    <dc:date>2010-03-08T04:07:14+00:00</dc:date>
    <link>http://www.rethinkdb.com/blog/2010/03/high-scalability-sql-and-computational-complexity/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[On computational complexity of SQL (the language) ]]></description>
<dc:subject>nosql sql scalability</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:sogrady/b:a56cfaacfacc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:nosql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:sql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.roadtofailure.com/2010/02/15/announcing-the-drawn-to-scale-platform/">
    <title>Announcing the Drawn-to-Scale Platform! | Road to Failure</title>
    <dc:date>2010-03-04T15:40:46+00:00</dc:date>
    <link>http://www.roadtofailure.com/2010/02/15/announcing-the-drawn-to-scale-platform/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[large scale data analytics, indexing and search...as a service. spoke with Bradford a week or two ago, and as i told him, this is an interesting proposition. as more folks realize the need for big data processing, the value of such services only goes up.]]></description>
<dc:subject>cloud database databases hadoop scalability scaling hbase drawntoscale</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:7e74e6bb376d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:databases"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:hbase"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:drawntoscale"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nosql.mypopescu.com/post/407159447/cassandra-twitter-an-interview-with-ryan-king">
    <title>Cassandra @ Twitter: An Interview with Ryan King « MyNoSQL</title>
    <dc:date>2010-03-04T12:46:53+00:00</dc:date>
    <link>http://nosql.mypopescu.com/post/407159447/cassandra-twitter-an-interview-with-ryan-king</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[details on Twitter's migration from MySQL to Cassandra
]]></description>
<dc:subject>twitter mysql nosql cassandra scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:2b74d78f26ab/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mysql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:nosql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cassandra"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://pl.atyp.us/wordpress/?p=2713">
    <title>Canned Platypus » Blog Archive » Getting Silly About NoSQL</title>
    <dc:date>2010-03-04T12:43:59+00:00</dc:date>
    <link>http://pl.atyp.us/wordpress/?p=2713</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[a rebuttal to Forbes' anti-NoSQL rant
]]></description>
<dc:subject>nosql dennisforbes sql scaling scalability mysql rdbms</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:8ec3897c5030/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:nosql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:dennisforbes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:sql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mysql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:rdbms"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.yafla.com/dforbes/Getting_Real_about_NoSQL_and_the_SQL_Isnt_Scalable_Lie">
    <title>Dennis Forbes on Software and Technology - Getting Real about NoSQL and the SQL-Isn't-Scalable Lie</title>
    <dc:date>2010-03-04T12:43:37+00:00</dc:date>
    <link>http://www.yafla.com/dforbes/Getting_Real_about_NoSQL_and_the_SQL_Isnt_Scalable_Lie</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[what is essentially an anti-NoSQL rant
]]></description>
<dc:subject>nosql dennisforbes sql scaling scalability mysql rdbms</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:a32434fe4cd1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:nosql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:dennisforbes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:sql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mysql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:rdbms"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tantannoodles.com/toolkit/wordpress-s3/">
    <title>Amazon S3 plugin for WordPress : tan tan noodles – msg free since 2005</title>
    <dc:date>2009-12-10T20:29:42+00:00</dc:date>
    <link>http://tantannoodles.com/toolkit/wordpress-s3/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[this is pretty interesting, if you serve static assets from your wordpress instance
]]></description>
<dc:subject>amazon s3 plugins wordpress scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:5c6e61c99b57/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:s3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:plugins"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:wordpress"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://groups.google.com/group/unladen-swallow/browse_thread/thread/4edbc406f544643e?pli=1">
    <title>Recommendation against Python? - Unladen Swallow | Google Groups</title>
    <dc:date>2009-11-11T20:59:21+00:00</dc:date>
    <link>http://groups.google.com/group/unladen-swallow/browse_thread/thread/4edbc406f544643e?pli=1</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[interesting, if unsurprising, commentary on the role of Python w/in Google
]]></description>
<dc:subject>google java programming python performance scalability architecture c++ via:rafe</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:4d57990c6afa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:java"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:c++"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:via:rafe"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.mongodb.org/display/DOCS/Comparing+Mongo+DB+and+Couch+DB">
    <title>Comparing Mongo DB and Couch DB - MongoDB</title>
    <dc:date>2009-11-11T17:28:19+00:00</dc:date>
    <link>http://www.mongodb.org/display/DOCS/Comparing+Mongo+DB+and+Couch+DB</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[Mongo compares itself to Couch: two next generation database options
]]></description>
<dc:subject>couchdb mongodb database cloud performance development scalability sysadmin nosql comparisons</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:9d7a39ad23d6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:couchdb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mongodb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:sysadmin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:nosql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:comparisons"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://jsensarma.com/blog/2009/11/dynamo-a-flawed-architecture-part-i/">
    <title>Dynamo: A flawed architecture - Part I « Joydeep Sen Sarma’s blog</title>
    <dc:date>2009-11-11T17:27:07+00:00</dc:date>
    <link>http://jsensarma.com/blog/2009/11/dynamo-a-flawed-architecture-part-i/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[pushback to Dynamo
]]></description>
<dc:subject>dynamo amazon scalability architecture distributed computing scaling nosql key-value eventual consistency</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:d96c97345df9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:dynamo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:computing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:nosql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:key-value"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:eventual"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:consistency"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.anchor.com.au/blog/2009/09/github-designing-success/">
    <title>Github Migration Architecture | Anchor Web Hosting Blog</title>
    <dc:date>2009-10-01T14:32:23+00:00</dc:date>
    <link>http://www.anchor.com.au/blog/2009/09/github-designing-success/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[how Github planned for its migration
]]></description>
<dc:subject>github migration architecture anchor infrastructure scalability cluster</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:fe22e4562427/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:migration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:anchor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cluster"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.digg.com/?p=966">
    <title>Digg the Blog » Blog Archive » Looking to the future with Cassandra</title>
    <dc:date>2009-09-10T20:43:45+00:00</dc:date>
    <link>http://blog.digg.com/?p=966</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[where are we going after databases? Cassandra is one answer popping up more and more
]]></description>
<dc:subject>digg database performance cassandra nosql architecture hashtable scalability key-value</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:130b99623410/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:digg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cassandra"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:nosql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:hashtable"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:key-value"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://googleappengine.blogspot.com/2009/02/back-to-future-for-data-storage.html">
    <title>Back to the Future for Data Storage</title>
    <dc:date>2009-02-23T21:00:05+00:00</dc:date>
    <link>http://googleappengine.blogspot.com/2009/02/back-to-future-for-data-storage.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[really excellent piece by Joe that summarizes far more succinctly than I ever have the rapidly evolving database options beyond the one-size-fits-all relational approach.
]]></description>
<dc:subject>joegregorio programming hypertable couchdb simpledb databases distributed relational scalability cloudcomputing bigtable gae</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:4a59375763ff/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:joegregorio"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:hypertable"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:couchdb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:simpledb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:databases"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:relational"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cloudcomputing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:bigtable"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:gae"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://jeremy.zawodny.com/blog/archives/010774.html">
    <title>The New MySQL Landscape (by Jeremy Zawodny)</title>
    <dc:date>2008-12-14T04:22:45+00:00</dc:date>
    <link>http://jeremy.zawodny.com/blog/archives/010774.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[really interesting look at the current ySQL landscape by one who knows it well, and has a lot of history in it
]]></description>
<dc:subject>jeremyzawodny mysql drizzle development database scalability percona opensource</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:07bdf494a06f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:jeremyzawodny"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mysql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:drizzle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:percona"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.25hoursaday.com/weblog/2008/11/03/WindowsAzureFromADevelopersPerspective.aspx">
    <title>Dare Obasanjo aka Carnage4Life - Windows Azure from a Developer's Perspective</title>
    <dc:date>2008-11-04T19:10:13+00:00</dc:date>
    <link>http://www.25hoursaday.com/weblog/2008/11/03/WindowsAzureFromADevelopersPerspective.aspx</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[one perspective on Azure
]]></description>
<dc:subject>windows web software saas microsoft cloud azure rest programming platform scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:b6252314ebf0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:windows"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:saas"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:microsoft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:azure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:platform"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.theregister.co.uk/2008/11/03/dziuba_azure/">
    <title>What Ray Ozzie didn't tell you about Microsoft Azure • The Register</title>
    <dc:date>2008-11-04T19:09:18+00:00</dc:date>
    <link>http://www.theregister.co.uk/2008/11/03/dziuba_azure/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[another perspective on Azure
]]></description>
<dc:subject>services scalability programming news microsoft google lockin complexity simple amazon azure</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:127daa0ae948/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:services"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:news"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:microsoft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:lockin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:complexity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:simple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:azure"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://roy.gbiv.com/untangled/2008/paper-tigers-and-hidden-dragons">
    <title>Paper tigers and hidden dragons » Untangled</title>
    <dc:date>2008-09-05T16:57:26+00:00</dc:date>
    <link>http://roy.gbiv.com/untangled/2008/paper-tigers-and-hidden-dragons</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["The point is that you don’t need to change technologies (or even interaction styles) to solve a problem of information transfer efficiency. Sometimes you just need to rethink the problem. There are many systems for which a different architecture is far more efficient, just as XMPP is far more efficient than HTTP for something like group chat. Large-scale collaborative monitoring is not one of them. An XMPP solution is far more applicable to peer-to-peer monitoring, where there is no central service that is interested in the entire state of a big site like Flickr, but even then we have to keep in mind that the economics of the crowd will dictate scalability, not the protocol used for information transfer."
]]></description>
<dc:subject>royfielding xmpp http web software scalability pubsub scaling notification messaging performance</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:2db55337f5a8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:royfielding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:xmpp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:pubsub"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:notification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:messaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://hadoop.apache.org/hbase/">
    <title>Welcome to HBase!</title>
    <dc:date>2008-07-14T14:07:46+00:00</dc:date>
    <link>http://hadoop.apache.org/hbase/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[interesting.
]]></description>
<dc:subject>apache appengine big bigtable cluster clustering couchdb data database hadoop hbase distributed scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:33038b123511/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:apache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:appengine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:big"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:bigtable"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cluster"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:clustering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:couchdb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:hbase"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.russellbeattie.com/blog/let-the-microblogs-bloom">
    <title>Let the microblogs bloom - RussellBeattie.com</title>
    <dc:date>2008-07-07T01:33:00+00:00</dc:date>
    <link>http://www.russellbeattie.com/blog/let-the-microblogs-bloom</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["It's a great effort, looks good....Evan...did a great job creating a nice little project with some cool features like OpenID, Jabber support and the beginnings of a federation system. Looking at the code, however, it's doomed."
]]></description>
<dc:subject>russellbeattie twitter microblogging architecture scalability scaling development programming laconica identica via:luis</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:96487af4c5db/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:russellbeattie"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:microblogging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:laconica"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:identica"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:via:luis"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blogs.smugmug.com/don/2008/06/03/skynet-lives-aka-ec2-smugmug/">
    <title>SmugBlog: Don MacAskill » Blog Archive » SkyNet Lives! (aka EC2 @ SmugMug)</title>
    <dc:date>2008-06-04T01:28:35+00:00</dc:date>
    <link>http://blogs.smugmug.com/don/2008/06/03/skynet-lives-aka-ec2-smugmug/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["I really don’t want to operate datacenters anymore despite the fact that we’re pretty good at it. It’s a necessary evil because we’re an Internet company, but our mission is to be the best photo sharing site." - Skynet = their GAE abstraction lay
]]></description>
<dc:subject>donmacaskill ec2 amazon scalability smugmug s3 aws architecture cloud skynet</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:470e07c309c3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:donmacaskill"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:ec2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:smugmug"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:s3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:skynet"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.twitter.com/2008/05/its-not-rocket-science-but-its-our-work.html">
    <title>Twitter Blog: It's Not Rocket Science, But It's Our Work</title>
    <dc:date>2008-06-01T23:16:38+00:00</dc:date>
    <link>http://blog.twitter.com/2008/05/its-not-rocket-science-but-its-our-work.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[Twitter's got nothing to be ashamed of, in my view. yes, their architecture is ill conceived and poorly thought out, but so it has been for most of the startups i've know. their transparency here does them credit, IMO.
]]></description>
<dc:subject>twitter community future scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:120958b9bf3c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:future"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ma.tt/2008/05/infrastructure-as-competitive-advantage/">
    <title>Ma.tt » Infrastructure as Competitive Advantage</title>
    <dc:date>2008-05-13T19:03:38+00:00</dc:date>
    <link>http://ma.tt/2008/05/infrastructure-as-competitive-advantage/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["Infrastructure can be a competitive advantage today — the speed and reliability of WordPress.com has certainly put us in a favorable light with users, especially large customers — but that’s going to disappear over time."
]]></description>
<dc:subject>infrastructure scaling wordpress mattmullenweg cloud scalability performance googlegears cdn</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:7f75d01ad873/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:wordpress"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mattmullenweg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:googlegears"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cdn"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://highscalability.com/google-appengine-second-look">
    <title>Google AppEngine - A Second Look | High Scalability</title>
    <dc:date>2008-04-13T20:31:28+00:00</dc:date>
    <link>http://highscalability.com/google-appengine-second-look</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["What's more the problem is developers will be acquiring a sort of learned helplessness. It's not that developers can't port to another environment, they simply won't know how to anymore because they will have never had to do it themselves."
]]></description>
<dc:subject>google appengine scalability bigtable gae architecture python learnedhelplessness</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:b6f4fb0f7273/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:appengine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:bigtable"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:gae"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:learnedhelplessness"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.techcrunch.com/2008/04/04/source-google-to-launch-bigtable-as-web-service/">
    <title>Source: Google To Launch BigTable As Web Service</title>
    <dc:date>2008-04-07T18:55:19+00:00</dc:date>
    <link>http://www.techcrunch.com/2008/04/04/source-google-to-launch-bigtable-as-web-service/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["Google may be releasing BigTable...as a web service to compete with Amazon SimpleDB, according to a source...There are also rumors that press is being pre-briefed on the product, although we haven’t been contacted by Google." nor have we
]]></description>
<dc:subject>google database bigtable cloud amazon scalability computing</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:acd1cd305a27/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:bigtable"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:computing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://radlab.cs.berkeley.edu/wiki/RAD_Lab">
    <title>RAD Lab - RAD Lab</title>
    <dc:date>2008-02-22T15:54:54+00:00</dc:date>
    <link>http://radlab.cs.berkeley.edu/wiki/RAD_Lab</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["Our vision is to enable one person to invent and run the next revolutionary IT service, operationally expressing a new business idea as a multi-million-user service over the course of a long weekend." - good luck with that. still, interesting.
]]></description>
<dc:subject>rad research distributed technology google scalability datacenter</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:aa44b0437581/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:rad"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:datacenter"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://developer.yahoo.com/blogs/hadoop/2008/02/yahoo-worlds-largest-production-hadoop.html">
    <title>Yahoo! Launches World's Largest Hadoop Production Application (Hadoop and Distributed Computing at Yahoo!)</title>
    <dc:date>2008-02-20T02:56:32+00:00</dc:date>
    <link>http://developer.yahoo.com/blogs/hadoop/2008/02/yahoo-worlds-largest-production-hadoop.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["Yahoo! recently launched what we believe is the worlds largest Apache Hadoop production application. The Yahoo! Search Webmap is a Hadoop application that runs on a more than 10,000 core Linux cluster"
]]></description>
<dc:subject>apache hadoop infrastructure java mapreduce opensource scalability yahoo</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:7ade4cfaba96/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:apache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:java"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mapreduce"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:yahoo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://googlesystem.blogspot.com/2008/01/google-reveals-more-mapreduce-stats.html">
    <title>Google Reveals New MapReduce Stats</title>
    <dc:date>2008-01-11T04:54:06+00:00</dc:date>
    <link>http://googlesystem.blogspot.com/2008/01/google-reveals-more-mapreduce-stats.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[just what it says
]]></description>
<dc:subject>google mapreduce performance scalability data volume</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:f1d9431082f7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mapreduce"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:volume"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.igvita.com/2007/12/28/thrudb-faster-and-cheaper-than-simpledb/">
    <title>Thrudb - faster, cheaper than SimpleDB - igvita.com</title>
    <dc:date>2007-12-28T19:57:24+00:00</dc:date>
    <link>http://www.igvita.com/2007/12/28/thrudb-faster-and-cheaper-than-simpledb/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["Developed by Jake Luciani as part of his ThruDB platform which currently powers JunkDepot, it is a highly scalable document-oriented database ideal for deployment on virtual (Amazon EC2+S3) or dedicated infrastructure."
]]></description>
<dc:subject>thrudb thrudoc ec2 s3 couchdb aws amazon berkeleydb database scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:c157ba11eed5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:thrudb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:thrudoc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:ec2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:s3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:couchdb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:berkeleydb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.allthingsdistributed.com/2007/12/eventually_consistent.html">
    <title>Eventually Consistent - All Things Distributed</title>
    <dc:date>2007-12-20T16:40:49+00:00</dc:date>
    <link>http://www.allthingsdistributed.com/2007/12/eventually_consistent.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["Inconsistency can tolerated for two reasons...Whether or not inconsistencies are acceptable depends on the client application."
]]></description>
<dc:subject>eventual consistency amazon architecture database distributed distributed-computing scalability wernervogels</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:5235bbbd5c6d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:eventual"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:consistency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:distributed-computing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:wernervogels"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bitworking.org/news/276/On-the-importance-of-being-megadata">
    <title>Joe Gregorio | BitWorking | On the importance of being megadata</title>
    <dc:date>2007-12-20T16:01:44+00:00</dc:date>
    <link>http://bitworking.org/news/276/On-the-importance-of-being-megadata</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["Amazon has opened SimpleDB for beta testers. As you would expect the system is designed to scale and as such has dropped generic relational operations such as joins and transactions."
]]></description>
<dc:subject>joegregorio amazon architecture database megadata scalability simpledb saas haas</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:cbf24a606555/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:joegregorio"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:megadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:simpledb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:saas"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:haas"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://aws.typepad.com/aws/2007/10/amazon-ec2-gets.html">
    <title>Amazon Web Services Blog: Amazon EC2 Gets More Muscle</title>
    <dc:date>2007-10-16T21:06:52+00:00</dc:date>
    <link>http://aws.typepad.com/aws/2007/10/amazon-ec2-gets.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[all good, except for the "EC2 Compute Unit" - that sounds like MIPS all over again
]]></description>
<dc:subject>amazon ec2 64bit applications cpu ram scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:a29cc2d2b45d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:ec2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:64bit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:applications"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cpu"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:ram"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.flickr.com/photos/8821087@N07/1432492939/">
    <title>Screenshot-1 on Flickr - Photo Sharing!</title>
    <dc:date>2007-09-24T19:40:59+00:00</dc:date>
    <link>http://www.flickr.com/photos/8821087@N07/1432492939/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[interesting performance results for linux-rt
]]></description>
<dc:subject>realtime linux rhel tibco messaging performance scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:8ec59839ab04/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:rhel"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:tibco"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:messaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://patricklogan.blogspot.com/2007/09/amqp-xmpp.html">
    <title>Making it stick.: AMQP, XMPP</title>
    <dc:date>2007-09-18T00:20:23+00:00</dc:date>
    <link>http://patricklogan.blogspot.com/2007/09/amqp-xmpp.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["I think we have a lot to learn still about how simple the enterprise can eventually be." - yes, precisely
]]></description>
<dc:subject>architecture notification software xmpp amqp messaging scalability enterprise simplicity via:planetintertwinglymemes</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:74003da76ff3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:notification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:xmpp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:amqp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:messaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:enterprise"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:simplicity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:via:planetintertwinglymemes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://highscalability.com/demand-infinitely-scalable-database-seed-amazon-ec2-cloud">
    <title>On-Demand Infinitely Scalable Database Seed the Amazon EC2 Cloud | High Scalability</title>
    <dc:date>2007-09-14T01:57:57+00:00</dc:date>
    <link>http://highscalability.com/demand-infinitely-scalable-database-seed-amazon-ec2-cloud</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[does the model have problems? you bet. is it general purpose yet? nope. but is it a sign of things to come? absolutely yes, IMO.
]]></description>
<dc:subject>hosted haas saas amazon elastra ec2 s3 dbms scalability via:sequeira</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:521f0015f4ce/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:hosted"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:haas"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:saas"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:elastra"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:ec2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:s3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:dbms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:via:sequeira"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.sauria.com/blog/2007/08/25/scalability-concurrency/">
    <title>Ted Leung on the Air » Blog Archive » Scalability != concurrency</title>
    <dc:date>2007-08-26T17:07:12+00:00</dc:date>
    <link>http://www.sauria.com/blog/2007/08/25/scalability-concurrency/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["It is certainly possible to scale a program written in any language - that’s a given. Especially when scaling = throwing more hardware at it. But there’s got to be a better way...Question is whether the better way is worth the price of admission."
]]></description>
<dc:subject>concurrency scalability tedleung erlang java samruby</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:bb9c65311554/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:concurrency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:tedleung"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:erlang"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:java"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:samruby"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dev.gentoo.org/~dberkholz/oscon/filesystem-notes.txt">
    <title>http://dev.gentoo.org/~dberkholz/oscon/filesystem-notes.txt</title>
    <dc:date>2007-07-27T19:18:57+00:00</dc:date>
    <link>http://dev.gentoo.org/~dberkholz/oscon/filesystem-notes.txt</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[very useful summary of Val Henson's filesystem talk from last year's OSCON (thx, Donnie)
]]></description>
<dc:subject>oscon valhenson filesystems opensource scalability via:dberkholz</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:c98a954eff7b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:oscon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:valhenson"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:filesystems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:via:dberkholz"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://cfis.savagexi.com/articles/2007/07/18/making-rails-go-vroom">
    <title>Making Rails Go Vroom</title>
    <dc:date>2007-07-19T02:01:31+00:00</dc:date>
    <link>http://cfis.savagexi.com/articles/2007/07/18/making-rails-go-vroom</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[tuning up Rails
]]></description>
<dc:subject>charliesavage rails ruby performance scalability scaling</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:255233b318bd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:charliesavage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scaling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://funkatron.com/index.php/site/comments/what-matt-mullenweg-doesnt-know-about-php5-and-how-it-hurts-him-and-his-use/">
    <title>funkatron.com : What Matt Mullenweg doesn’t know about PHP5, and how it hurts him and his users</title>
    <dc:date>2007-07-17T15:04:52+00:00</dc:date>
    <link>http://funkatron.com/index.php/site/comments/what-matt-mullenweg-doesnt-know-about-php5-and-how-it-hurts-him-and-his-use/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[pushback to Matt's thoughts on PHP 5; it's a complicated issue, obviously
]]></description>
<dc:subject>mattmullenweg php php5 security scalability objectoriented</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:f736f8dd9d6a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mattmullenweg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:php5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:objectoriented"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kylecordes.com/2007/07/12/youtube-scalability/">
    <title>YouTube Scalability Talk - Kyle Cordes</title>
    <dc:date>2007-07-17T15:03:43+00:00</dc:date>
    <link>http://kylecordes.com/2007/07/12/youtube-scalability/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[fascinating talk from the YouTube guys on scalability
]]></description>
<dc:subject>architecture clustering code concurrency databases scalability megadata via:joe</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:1f15379a8b78/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:clustering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:concurrency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:databases"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:megadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:via:joe"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.dehora.net/journal/2007/06/comparative_architecture.html">
    <title>Bill de hÓra: Comparative Architecture</title>
    <dc:date>2007-06-15T14:46:23+00:00</dc:date>
    <link>http://www.dehora.net/journal/2007/06/comparative_architecture.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["In my part of the world, Scala doesn't make Google results front page. Give it a month." - if that
]]></description>
<dc:subject>billdeh scala scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:117a10851d40/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:billdeh"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scala"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.leetsoft.com/2007/5/22/the-secret-to-memcached">
    <title>Too-biased - Tobias Luetke's thoughts</title>
    <dc:date>2007-05-23T21:32:37+00:00</dc:date>
    <link>http://blog.leetsoft.com/2007/5/22/the-secret-to-memcached</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[specifics on memcached, including some really amazing anecdotal evidence; Facebook's using memcached on 3TBs of RAM? really?
]]></description>
<dc:subject>memcached facebook caching performance scalability lamp</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:91177aabd206/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:memcached"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:caching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:lamp"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.artima.com/scalazine/articles/steps.html">
    <title>First Steps to Scala</title>
    <dc:date>2007-05-15T21:28:25+00:00</dc:date>
    <link>http://www.artima.com/scalazine/articles/steps.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[had a presentation on this at RedMonkOne - will have to track it with respect to adoption
]]></description>
<dc:subject>redmonkone scala lift framework scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:eab6b9f1b3ef/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:redmonkone"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scala"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:lift"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.jsequeira.com/blog/2007/05/09.html#a894">
    <title>John Sequeira's Weblog</title>
    <dc:date>2007-05-09T19:52:12+00:00</dc:date>
    <link>http://www.jsequeira.com/blog/2007/05/09.html#a894</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["If you google for Twitter and scalability, you'll find a lot of articles on how Twitter's Rails setup has buckled under their obscene growth curve...But I think that fundamentally they're using the wrong technology for what they're trying to accomplish."
]]></description>
<dc:subject>johnsequeira twitter scalability streambase vertica eventprocessing messaging framework</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:5f9a36a9f6d2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:johnsequeira"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:streambase"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:vertica"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:eventprocessing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:messaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:framework"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tomayko.com/weblog/2007/04/13/rails-multiple-connections">
    <title>Rails and Scaling with Multiple Databases</title>
    <dc:date>2007-04-13T21:43:39+00:00</dc:date>
    <link>http://tomayko.com/weblog/2007/04/13/rails-multiple-connections</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[great pushback from Ryan on some of the criticisms leveled at Rails by the Twitter crew
]]></description>
<dc:subject>rails ryantomayko databases pooling connection scalability performance postgresql design</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:a392ba2b3331/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:ryantomayko"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:databases"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:pooling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:connection"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:postgresql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.loudthinking.com/arc/000608.html">
    <title>Twitter trouble (Loud Thinking)</title>
    <dc:date>2007-04-13T00:04:10+00:00</dc:date>
    <link>http://www.loudthinking.com/arc/000608.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[DHH's pushback on some the Rails criticisms from the Twitter interview
]]></description>
<dc:subject>davidheinemeier-hansson rails twitter performance bottlenecks scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:a2639126a768/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:davidheinemeier-hansson"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:bottlenecks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.nanobeepers.com/2007/04/07/infinitely-scalable-framework-with-aws/">
    <title>Nanobeepers » Infinitely Scalable Framework with AWS?</title>
    <dc:date>2007-04-09T23:29:41+00:00</dc:date>
    <link>http://blog.nanobeepers.com/2007/04/07/infinitely-scalable-framework-with-aws/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[seen over on Joe's Megadata post: another option built on Amazon's HaaS offerings
]]></description>
<dc:subject>s3 ec2 aws haas persistence scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:c2283cb1597c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:s3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:ec2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:haas"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:persistence"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bitworking.org/news/158/ETech-07-Summary-Part-2-MegaData">
    <title>Joe Gregorio | BitWorking | ETech '07 Summary - Part 2 - MegaData</title>
    <dc:date>2007-04-09T23:09:09+00:00</dc:date>
    <link>http://bitworking.org/news/158/ETech-07-Summary-Part-2-MegaData</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[if you liked Adam Bosworth's "Where Have All the Good Databases Gone", this is important, just trust me (see also Bill's comments); on a completely unrelated note, great to meet Joe in person - albeit briefly - last week
]]></description>
<dc:subject>joegregorio databases storage scalability joinless distributed bigdata</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:dfd2e3011a17/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:joegregorio"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:databases"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:storage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:joinless"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:bigdata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://joyeur.com/2007/04/03/thinking-about-uptime-numbers-for-the-top-20-websites">
    <title>Joyeur: Joyeur: Thinking about uptime numbers for the top 20 websites</title>
    <dc:date>2007-04-03T16:30:34+00:00</dc:date>
    <link>http://joyeur.com/2007/04/03/thinking-about-uptime-numbers-for-the-top-20-websites</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["Does 4 hours and 47 minutes of downtime for blogger.com over-estimate or under-estimate the availability of myblog.blogspot.com?" - good question, don't know the answer
]]></description>
<dc:subject>availability scalability uptime joyeur blogger flickr</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:a1fe7c4830da/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:availability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:uptime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:joyeur"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:blogger"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:flickr"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://swik.net/User:alex/Alex+Bosworth+-+The+Races/The+New+Black%3F+Twitter.com/zw6l">
    <title>User:alex : Alex Bosworth - The Races : The New Black? Twitter.com - SWiK</title>
    <dc:date>2007-03-12T08:52:13+00:00</dc:date>
    <link>http://swik.net/User:alex/Alex+Bosworth+-+The+Races/The+New+Black%3F+Twitter.com/zw6l</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[Alex, however, is less than impressed with the scalability; i actually haven't seen these problems yet myself
]]></description>
<dc:subject>alexbosworth twitter scalability popularity joyeur</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:f0fc3b6984ae/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:alexbosworth"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:popularity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:joyeur"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://joyeur.com/2007/03/10/my-heart-twitters-when-i-see-this-chart">
    <title>Joyeur: Joyeur: My Heart Twitters When I See This Chart</title>
    <dc:date>2007-03-12T08:50:42+00:00</dc:date>
    <link>http://joyeur.com/2007/03/10/my-heart-twitters-when-i-see-this-chart</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[Joyeur folks happy for one of their customers that is positively exploding in terms of popularity
]]></description>
<dc:subject>twitter joyeur scalability accelerators</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:9d8b143e3dcf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:joyeur"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:accelerators"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.gregwhitescarver.com/blog/2007/02/03/scaling-mysql-thoughts-on-replication-sharding-and-mysql-cluster/">
    <title>Code and Whatnot » Blog Archive » Scaling MySQL: thoughts on replication, sharding, and MySQL Cluster</title>
    <dc:date>2007-02-12T21:43:02+00:00</dc:date>
    <link>http://www.gregwhitescarver.com/blog/2007/02/03/scaling-mysql-thoughts-on-replication-sharding-and-mysql-cluster/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[some very interesting thoughts on clustering and scaling MySQL from Greg; most important, note his discussion of the difference between speed and scalability
]]></description>
<dc:subject>mysql whitecarver scalability speed performance flickr php clustering replication sharding</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:be51e5c1e37b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mysql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:whitecarver"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:speed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:flickr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:clustering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:replication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:sharding"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blogs.zdnet.com/BTL/?p=4308">
    <title>» MySpace: IT on a wing and a Microsoft prayer | Between the Lines | ZDNet.com</title>
    <dc:date>2007-01-21T16:05:49+00:00</dc:date>
    <link>http://blogs.zdnet.com/BTL/?p=4308</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[thoughts on MySpace and scaling up on Microsoft
]]></description>
<dc:subject>microsoft myspace scalability windows</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:5a0c3153fcb8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:microsoft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:myspace"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:windows"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.amber.org/2006/12/11/the-availability-game/">
    <title>The availability game : Pensieri di un lunatico minore</title>
    <dc:date>2006-12-17T20:01:48+00:00</dc:date>
    <link>http://blog.amber.org/2006/12/11/the-availability-game/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["I usually tell people that every additional nine costs 2x what the previous one cost...You best be able to write a business case for that." - precisely; great to see others making the case for sanity
]]></description>
<dc:subject>petrilli availability scalability economics cost</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:e3f955bd899c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:petrilli"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:availability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:economics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cost"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.jonathanboutelle.com/mt/archives/2006/12/scalable_web_ar.html">
    <title>Scalable Web Architectures with Ruby and Amazon S3</title>
    <dc:date>2006-12-08T00:14:22+00:00</dc:date>
    <link>http://www.jonathanboutelle.com/mt/archives/2006/12/scalable_web_ar.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA["I focused on what we learned from building slideshare, including aspects specific to scaling Ruby on Rails." - slides are nice and useful
]]></description>
<dc:subject>s3 ruby amazon rails scalability mongrel mogilefs nagios pound</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:2b3d8347a019/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:s3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mongrel"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mogilefs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:nagios"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:pound"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://feh.holsman.net/articles/2006/06/28/memcached-performance">
    <title>memcached performance</title>
    <dc:date>2006-06-29T17:06:06+00:00</dc:date>
    <link>http://feh.holsman.net/articles/2006/06/28/memcached-performance</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[the post that pointed me to some of the memcached posts, with some thoughts on improving DJango
]]></description>
<dc:subject>django feh apache scalability performance</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:a2e054dea66c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:django"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:feh"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:apache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://lists.danga.com/pipermail/memcached/2006-June/002384.html">
    <title>Memcached as a Sessions Store (etc)</title>
    <dc:date>2006-06-29T17:02:43+00:00</dc:date>
    <link>http://lists.danga.com/pipermail/memcached/2006-June/002384.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[very interesting discussion of Digg's back end
]]></description>
<dc:subject>memcached mysql scalability digg via:feh performance cache scale</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:e60247ce2f09/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:memcached"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mysql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:digg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:via:feh"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:cache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scale"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dealnews.com/developers/memcached.html">
    <title>Fastest languages for memcached</title>
    <dc:date>2006-06-29T17:00:01+00:00</dc:date>
    <link>http://dealnews.com/developers/memcached.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[interesting benchmarks for the P languages on Apache
]]></description>
<dc:subject>perl python php apache via:feh benchmarks scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:db8515b277ac/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:perl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:apache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:via:feh"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:benchmarks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.topix.net/archives/000045.html">
    <title>Topix.net Weblog: Topix.net Architecture</title>
    <dc:date>2006-05-08T05:59:59+00:00</dc:date>
    <link>http://blog.topix.net/archives/000045.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[more props for flat files from the Topix guys
]]></description>
<dc:subject>topix databases files flat google filesystem kiss linux mysql rdbms scalability search</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:5cff1991423d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:topix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:databases"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:files"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:flat"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:filesystem"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:kiss"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mysql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:rdbms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:search"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://radar.oreilly.com/archives/2006/05/database_war_stories_8_findory_1.html">
    <title>O'Reilly Radar &gt; Database War Stories #8: Findory and Amazon</title>
    <dc:date>2006-05-08T05:50:39+00:00</dc:date>
    <link>http://radar.oreilly.com/archives/2006/05/database_war_stories_8_findory_1.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[more anecdotes via O'Reilly on database trends; this one is via Findory's Linden
]]></description>
<dc:subject>linden o'reilly databases flat files mysql scalability amazon findory relational</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:fbdb9a6bc3bd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:linden"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:o'reilly"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:databases"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:flat"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:files"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mysql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:findory"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:relational"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://weblog.rubyonrails.com/articles/2006/03/07/2-5-million-requests">
    <title>2.5 Million Requests</title>
    <dc:date>2006-03-08T07:17:19+00:00</dc:date>
    <link>http://weblog.rubyonrails.com/articles/2006/03/07/2-5-million-requests</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[some anecdotal information on Ruby on Rails scalability
]]></description>
<dc:subject>ruby rubyonrails scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:5bc7ad5b9954/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:rubyonrails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://pezra.barelyenough.org/blog/2006/02/dynamic-languages-and-the-jvm/#footnote-link-1-207">
    <title>Peter Williams’ Weblog » Dynamic Languages and the JVM</title>
    <dc:date>2006-02-23T18:56:26+00:00</dc:date>
    <link>http://pezra.barelyenough.org/blog/2006/02/dynamic-languages-and-the-jvm/#footnote-link-1-207</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[Peter's thoughts on dynamic languages and the JVM; in particular, check out the comments on Erlang - i'm hearing that mentioned more and more
]]></description>
<dc:subject>erlang dynamic-languages python ruby perl php jvm scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:74bc51c815a7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:erlang"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:dynamic-languages"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:perl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:jvm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.tbray.org/ongoing/When/200x/2006/02/02/LAMP-Java-Sun">
    <title>ongoing · LAMP and Java</title>
    <dc:date>2006-02-07T01:06:03+00:00</dc:date>
    <link>http://www.tbray.org/ongoing/When/200x/2006/02/02/LAMP-Java-Sun</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[outstanding response from Tim on my Sun Analyst Conf piece - will be sure to respond in depth soon, hopefully tomorrow
]]></description>
<dc:subject>Bray tecosystems lamp java languages platform jython jruby caucho php ruby perl jvm threading scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:0073856f24e2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:Bray"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:tecosystems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:lamp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:java"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:languages"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:platform"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:jython"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:jruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:caucho"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:perl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:jvm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:threading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://feedlounge.com/blog/2006/01/29/update-2006-01-29/">
    <title>Update: 2006-01-29 : FeedLounge</title>
    <dc:date>2006-01-30T19:16:40+00:00</dc:date>
    <link>http://feedlounge.com/blog/2006/01/29/update-2006-01-29/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[FeedLounge guys using MogileFS and BerkeleyDB, alongside Postgres - this was one of the examples i had in mind with the post from last week
]]></description>
<dc:subject>feedlounge mogilefs berkeley postgres databases relational scalability</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:0788913ba4d1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:feedlounge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mogilefs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:berkeley"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:postgres"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:databases"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:relational"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://37signals.com/svn/archives2/dont_scale_99999_uptime_is_for_walmart.php">
    <title>Don't scale: 99.999% uptime is for Wal-Mart - Signal vs. Noise (by 37signals)</title>
    <dc:date>2005-12-07T05:18:54+00:00</dc:date>
    <link>http://37signals.com/svn/archives2/dont_scale_99999_uptime_is_for_walmart.php</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[more on the question of scalability from 37Signals' Fried
]]></description>
<dc:subject>scalability 37signals fried uptime wal-mart web2.0</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:f2ea2f211c2b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:37signals"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:fried"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:uptime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:wal-mart"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:web2.0"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.flickr.com/flickrblog/2005/10/lamp.html">
    <title>FlickrBlog</title>
    <dc:date>2005-12-06T20:34:59+00:00</dc:date>
    <link>http://blog.flickr.com/flickrblog/2005/10/lamp.html</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[interesting presentation from the Flickr guys on LAMP infrastructures
]]></description>
<dc:subject>apache lamp flickr mysql php scalability performance systems</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:7f241e11bae7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:apache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:lamp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:flickr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:mysql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:systems"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://feedlounge.com/blog/2005/12/05/state-of-feedlounge/">
    <title>FeedLounge - The State of FeedLounge</title>
    <dc:date>2005-12-05T21:04:43+00:00</dc:date>
    <link>http://feedlounge.com/blog/2005/12/05/state-of-feedlounge/</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[Alex on FeedLounge and scalability, the business model, release dates and more
]]></description>
<dc:subject>feedlounge king aggregator ajax scalability business-models yahoo google</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:dc59f5fe485c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:feedlounge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:king"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:aggregator"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:ajax"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:business-models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:yahoo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:google"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://acmqueue.com/modules.php?name=Content&amp;pa=showpage&amp;pid=337">
    <title>ACM Queue - Learning from THE WEB - The Web has taught us many lessons about distributed computing, but some of the most important ones have yet to fully take hold.</title>
    <dc:date>2005-11-21T20:49:10+00:00</dc:date>
    <link>http://acmqueue.com/modules.php?name=Content&amp;pa=showpage&amp;pid=337</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[great summary of some of Bosworth's previous thoughts
]]></description>
<dc:subject>bosworth atom kiss databases distributed-systems google html performance scalability simplicity sloppy web2.0</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:c1606df74143/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:bosworth"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:atom"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:kiss"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:databases"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:distributed-systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:simplicity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:sloppy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:web2.0"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://jroller.com/page/bsnyder?entry=postgresql_architecture_discussion">
    <title>BruceBlog</title>
    <dc:date>2005-11-14T02:33:45+00:00</dc:date>
    <link>http://jroller.com/page/bsnyder?entry=postgresql_architecture_discussion</link>
    <dc:creator>sogrady</dc:creator><description><![CDATA[Bruce has questions about Postgres's scalability
]]></description>
<dc:subject>postgres snyder scalability opensource database</dc:subject>
<dc:identifier>https://pinboard.in/u:sogrady/b:cd5ad93cf200/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:postgres"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:snyder"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:sogrady/t:database"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>