<?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: Splitting Applications or Services for Scale</title>
	<atom:link href="http://akfpartners.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/feed/" rel="self" type="application/rss+xml" />
	<link>http://akfpartners.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/</link>
	<description>The Scalability Blog</description>
	<lastBuildDate>Tue, 10 Apr 2012 23:04:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Independence Day &#124; AKF Partners Blog</title>
		<link>http://akfpartners.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/#comment-55</link>
		<dc:creator>Independence Day &#124; AKF Partners Blog</dc:creator>
		<pubDate>Sat, 04 Jul 2009 12:45:46 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/#comment-55</guid>
		<description>[...] doing the same thing over and expecting different results. Learn or teach your team how to scale applications and databases. Go even further and declare your freedom from relational databases and get rid of [...]</description>
		<content:encoded><![CDATA[<p>[...] doing the same thing over and expecting different results. Learn or teach your team how to scale applications and databases. Go even further and declare your freedom from relational databases and get rid of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abbott, Keeven, Fisher &#38;#038 Fortuna Partners</title>
		<link>http://akfpartners.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/#comment-54</link>
		<dc:creator>Abbott, Keeven, Fisher &#38;#038 Fortuna Partners</dc:creator>
		<pubDate>Sat, 18 Apr 2009 10:55:22 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/#comment-54</guid>
		<description>[...] do so best in fact when not on a single server. This is the principle behind all three axes of the AKF Scale Cube. [...]</description>
		<content:encoded><![CDATA[<p>[...] do so best in fact when not on a single server. This is the principle behind all three axes of the AKF Scale Cube. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abbott, Keeven, Fisher &#38;#038 Fortuna Partners</title>
		<link>http://akfpartners.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/#comment-53</link>
		<dc:creator>Abbott, Keeven, Fisher &#38;#038 Fortuna Partners</dc:creator>
		<pubDate>Fri, 02 Jan 2009 19:19:18 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/#comment-53</guid>
		<description>[...] your application or database:  Start this year thinking about how to split your application and database.   We recommend our cube model for both because working on all three axes gives you [...]</description>
		<content:encoded><![CDATA[<p>[...] your application or database:  Start this year thinking about how to split your application and database.   We recommend our cube model for both because working on all three axes gives you [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 10 of the Biggest Platform Development Mistakes - GigaOM</title>
		<link>http://akfpartners.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/#comment-52</link>
		<dc:creator>10 of the Biggest Platform Development Mistakes - GigaOM</dc:creator>
		<pubDate>Mon, 30 Jun 2008 19:02:01 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/#comment-52</guid>
		<description>[...] 5) Scaling through third parties: If you&#8217;re a hyper-growth SaaS site, you don&#8217;t want to be locked into a vendor for your future business viability; rather you want to make sure that the scalability of your site is a core competency and that it&#8217;s built into your architecture. Define how your platform scales through your efforts, not through the systems that a third-party vendor provides. [...]</description>
		<content:encoded><![CDATA[<p>[...] 5) Scaling through third parties: If you&#8217;re a hyper-growth SaaS site, you don&#8217;t want to be locked into a vendor for your future business viability; rather you want to make sure that the scalability of your site is a core competency and that it&#8217;s built into your architecture. Define how your platform scales through your efforts, not through the systems that a third-party vendor provides. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abbott, Keeven &#38;#038 Fisher Consulting</title>
		<link>http://akfpartners.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/#comment-51</link>
		<dc:creator>Abbott, Keeven &#38;#038 Fisher Consulting</dc:creator>
		<pubDate>Thu, 26 Jun 2008 20:01:13 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/#comment-51</guid>
		<description>[...] A key skill or experience to look for in the Scalability Architect is a thorough knowledge of how to split both the application as well as the database in multiple dimensions, see our application and database splitting posts.  Additionally, the ideal candidate will have been through several of these splits before where they have learned some of the pitfalls.  Knowing that you need to consider what objects need to be cached with each other can save a lot of redesign and headache. [...]</description>
		<content:encoded><![CDATA[<p>[...] A key skill or experience to look for in the Scalability Architect is a thorough knowledge of how to split both the application as well as the database in multiple dimensions, see our application and database splitting posts.  Additionally, the ideal candidate will have been through several of these splits before where they have learned some of the pitfalls.  Knowing that you need to consider what objects need to be cached with each other can save a lot of redesign and headache. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

