<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Part 2: An Architecture Overview &#8212; Apache, MySQL, Memcached, SQLite</title>
	<atom:link href="http://www.derivante.com/2008/07/24/an-architecture-overview-apache-mysql-memcached-sqlite/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.derivante.com/2008/07/24/an-architecture-overview-apache-mysql-memcached-sqlite/</link>
	<description>to obtain or receive from a source</description>
	<lastBuildDate>Mon, 08 Mar 2010 16:36:12 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Owen Taylor</title>
		<link>http://www.derivante.com/2008/07/24/an-architecture-overview-apache-mysql-memcached-sqlite/comment-page-1/#comment-54</link>
		<dc:creator>Owen Taylor</dc:creator>
		<pubDate>Tue, 26 Aug 2008 04:11:07 +0000</pubDate>
		<guid isPermaLink="false">http://justinleider.wordpress.com/?p=11#comment-54</guid>
		<description>Your analysis of the scaling problem and solution are excellent.  I did a talk on this kind of architecture, but using a more avant-garde approach last Nov. [http://www.jroller.com/owentaylor/date/20080407]

I call it Transparent Partitioning &amp; Collocation.

To implement such a solution, I prefer to use memory more agressively.  Are you aware of GigaSpaces? - it is an in-memory partitioning solution that also runs on EC2.  From what I can tell it may suit your needs perfectly.

Let me know if you would like to hack something together.

Owen.</description>
		<content:encoded><![CDATA[<p>Your analysis of the scaling problem and solution are excellent.  I did a talk on this kind of architecture, but using a more avant-garde approach last Nov. [http://www.jroller.com/owentaylor/date/20080407]</p>
<p>I call it Transparent Partitioning &amp; Collocation.</p>
<p>To implement such a solution, I prefer to use memory more agressively.  Are you aware of GigaSpaces? &#8211; it is an in-memory partitioning solution that also runs on EC2.  From what I can tell it may suit your needs perfectly.</p>
<p>Let me know if you would like to hack something together.</p>
<p>Owen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlexM</title>
		<link>http://www.derivante.com/2008/07/24/an-architecture-overview-apache-mysql-memcached-sqlite/comment-page-1/#comment-52</link>
		<dc:creator>AlexM</dc:creator>
		<pubDate>Wed, 13 Aug 2008 14:29:06 +0000</pubDate>
		<guid isPermaLink="false">http://justinleider.wordpress.com/?p=11#comment-52</guid>
		<description>I found your site on technorati and read a few of your other posts. Keep up the good work. I just added your RSS feed to my Google News Reader. Looking forward to reading more from you down the road!</description>
		<content:encoded><![CDATA[<p>I found your site on technorati and read a few of your other posts. Keep up the good work. I just added your RSS feed to my Google News Reader. Looking forward to reading more from you down the road!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mackenzie</title>
		<link>http://www.derivante.com/2008/07/24/an-architecture-overview-apache-mysql-memcached-sqlite/comment-page-1/#comment-53</link>
		<dc:creator>Mackenzie</dc:creator>
		<pubDate>Tue, 05 Aug 2008 11:47:45 +0000</pubDate>
		<guid isPermaLink="false">http://justinleider.wordpress.com/?p=11#comment-53</guid>
		<description>Keep posting!  I would like to see this evolving.  Thanks for the insights already.</description>
		<content:encoded><![CDATA[<p>Keep posting!  I would like to see this evolving.  Thanks for the insights already.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->