<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Splitting Applications or Services for Scale</title>
	<link>http://akf-consulting.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/</link>
	<description>Technical and Leadership Thoughts</description>
	<pubDate>Thu, 20 Nov 2008 20:53:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: 10 of the Biggest Platform Development Mistakes - GigaOM</title>
		<link>http://akf-consulting.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/#comment-99</link>
		<pubDate>Mon, 30 Jun 2008 19:02:01 +0000</pubDate>
		<guid>http://akf-consulting.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/#comment-99</guid>
					<description>[...] 5) Scaling through third parties: If you&amp;#8217;re a hyper-growth SaaS site, you don&amp;#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&amp;#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>[&#8230;] 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. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Abbott, Keeven &#38;#038 Fisher Consulting</title>
		<link>http://akf-consulting.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/#comment-94</link>
		<pubDate>Thu, 26 Jun 2008 20:01:13 +0000</pubDate>
		<guid>http://akf-consulting.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/#comment-94</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>[&#8230;] 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. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.267 seconds -->
