<?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: The outer limits of scaling - how decentralized can your infrastructure be?</title>
	<atom:link href="http://jaybyjayfresh.com/2008/03/11/the-outer-limits-of-scaling-how-decentralized-can-your-infrastructure-be/feed/" rel="self" type="application/rss+xml" />
	<link>http://jaybyjayfresh.com/2008/03/11/the-outer-limits-of-scaling-how-decentralized-can-your-infrastructure-be/</link>
	<description>Right-on slack-jawed yokel-type tech-farmer</description>
	<pubDate>Thu, 04 Dec 2008 05:42:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andrew Back</title>
		<link>http://jaybyjayfresh.com/2008/03/11/the-outer-limits-of-scaling-how-decentralized-can-your-infrastructure-be/#comment-2349</link>
		<dc:creator>Andrew Back</dc:creator>
		<pubDate>Tue, 08 Apr 2008 12:46:37 +0000</pubDate>
		<guid isPermaLink="false">http://jaybyjayfresh.com/?p=116#comment-2349</guid>
		<description>The trouble with SLAs is that they cost money. Building and providing a basic service is relatively cheap compared to the cost in operational support systems. You still need some of these to provide a basic service that can scale Etc., but I'd assert that with fixed SLAs comes much additional complexity in terms of OSS. This is like the difference between your cheap or free web hosting, and say fully managed highly-available infrastructure such as major business outsources to BT.

Perhaps standards and data portability could help here: if it is easy to deploy logic and data to more than one location at once, and to move it around without major refactoring or transportation costs.

Agree with Fred on the current weakness of the SaaS/bank analogy. But then I'm sure when banks first came to be there was little in the way of regulation. But it may take a number of unfortunate incidents before governments put in place effective measures to protect SaaS consumers. 

But in any case I think service mash-ups most certainly have a brighter future than their musical counterparts - which quickly became tiring and a rather embarrassing source of momentary interest.</description>
		<content:encoded><![CDATA[<p>The trouble with SLAs is that they cost money. Building and providing a basic service is relatively cheap compared to the cost in operational support systems. You still need some of these to provide a basic service that can scale Etc., but I&#8217;d assert that with fixed SLAs comes much additional complexity in terms of OSS. This is like the difference between your cheap or free web hosting, and say fully managed highly-available infrastructure such as major business outsources to BT.</p>
<p>Perhaps standards and data portability could help here: if it is easy to deploy logic and data to more than one location at once, and to move it around without major refactoring or transportation costs.</p>
<p>Agree with Fred on the current weakness of the SaaS/bank analogy. But then I&#8217;m sure when banks first came to be there was little in the way of regulation. But it may take a number of unfortunate incidents before governments put in place effective measures to protect SaaS consumers. </p>
<p>But in any case I think service mash-ups most certainly have a brighter future than their musical counterparts - which quickly became tiring and a rather embarrassing source of momentary interest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FND</title>
		<link>http://jaybyjayfresh.com/2008/03/11/the-outer-limits-of-scaling-how-decentralized-can-your-infrastructure-be/#comment-2317</link>
		<dc:creator>FND</dc:creator>
		<pubDate>Sat, 15 Mar 2008 17:44:06 +0000</pubDate>
		<guid isPermaLink="false">http://jaybyjayfresh.com/?p=116#comment-2317</guid>
		<description>I'm with Andrew on this one - mashups are often great, but potentially volatile.

Aside: The SaaS/bank analogy doesn't stand up to close examination. For example, there are gazillions of regulations for financial institutions - but if your service provider shuts down, you mostly don't have any leverage.</description>
		<content:encoded><![CDATA[<p>I&#8217;m with Andrew on this one - mashups are often great, but potentially volatile.</p>
<p>Aside: The SaaS/bank analogy doesn&#8217;t stand up to close examination. For example, there are gazillions of regulations for financial institutions - but if your service provider shuts down, you mostly don&#8217;t have any leverage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jayfresh</title>
		<link>http://jaybyjayfresh.com/2008/03/11/the-outer-limits-of-scaling-how-decentralized-can-your-infrastructure-be/#comment-2316</link>
		<dc:creator>jayfresh</dc:creator>
		<pubDate>Fri, 14 Mar 2008 17:02:40 +0000</pubDate>
		<guid isPermaLink="false">http://jaybyjayfresh.com/?p=116#comment-2316</guid>
		<description>Andrew,

Thanks for the comment. My view on the reliability of mashups is that you only attempt to control the things you are capable of. I'll outsource reliability, scaling and dependability of my application to the people earning their living by providing a good level of service in those areas. If they aren't up to speed, I can move on and change my mashup to work with someone else.

As the demand for mashups increases, companies will start to offer SLA's to the people that want them. I'd thought &lt;a href="http://www.strikeiron.com" rel="nofollow"&gt;StrikeIron&lt;/a&gt; provided SLA's for the services they broker, but it would appear not. IBM has a &lt;a href="http://www.research.ibm.com/wsla/" rel="nofollow"&gt;research&lt;/a&gt; group looking into this.</description>
		<content:encoded><![CDATA[<p>Andrew,</p>
<p>Thanks for the comment. My view on the reliability of mashups is that you only attempt to control the things you are capable of. I&#8217;ll outsource reliability, scaling and dependability of my application to the people earning their living by providing a good level of service in those areas. If they aren&#8217;t up to speed, I can move on and change my mashup to work with someone else.</p>
<p>As the demand for mashups increases, companies will start to offer SLA&#8217;s to the people that want them. I&#8217;d thought <a href="http://www.strikeiron.com" rel="nofollow">StrikeIron</a> provided SLA&#8217;s for the services they broker, but it would appear not. IBM has a <a href="http://www.research.ibm.com/wsla/" rel="nofollow">research</a> group looking into this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Back</title>
		<link>http://jaybyjayfresh.com/2008/03/11/the-outer-limits-of-scaling-how-decentralized-can-your-infrastructure-be/#comment-2315</link>
		<dc:creator>Andrew Back</dc:creator>
		<pubDate>Thu, 13 Mar 2008 10:32:04 +0000</pubDate>
		<guid isPermaLink="false">http://jaybyjayfresh.com/?p=116#comment-2315</guid>
		<description>Interesting perspective and some great points, but I have a couple of issues in connection with mash-ups.

Reliability is inversely proportional to complexity, as suggested by the KISS principle. The mash-up by definition adds complexity, and furthermore reliance on 3rd parties with whom you likely have no formal contract or SLA. And  you are in essence at the mercy of their subject to change - or worse still fail - business models.

Would you build your house on land that had not been surveyed, and which you neither owned nor had a leasehold? Mash-ups bring many benefits but no certainty of scale, dependability or ongoing viability.</description>
		<content:encoded><![CDATA[<p>Interesting perspective and some great points, but I have a couple of issues in connection with mash-ups.</p>
<p>Reliability is inversely proportional to complexity, as suggested by the KISS principle. The mash-up by definition adds complexity, and furthermore reliance on 3rd parties with whom you likely have no formal contract or SLA. And  you are in essence at the mercy of their subject to change - or worse still fail - business models.</p>
<p>Would you build your house on land that had not been surveyed, and which you neither owned nor had a leasehold? Mash-ups bring many benefits but no certainty of scale, dependability or ongoing viability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-03-12 &#171; Treat with Jermolene</title>
		<link>http://jaybyjayfresh.com/2008/03/11/the-outer-limits-of-scaling-how-decentralized-can-your-infrastructure-be/#comment-2314</link>
		<dc:creator>links for 2008-03-12 &#171; Treat with Jermolene</dc:creator>
		<pubDate>Wed, 12 Mar 2008 18:18:47 +0000</pubDate>
		<guid isPermaLink="false">http://jaybyjayfresh.com/?p=116#comment-2314</guid>
		<description>[...] The outer limits of scaling - how decentralized can your infrastructure be? « Jay by Jay Fresh Jon explores the lure of smart clients and dumb servers&#8230; (tags: jonlister scalability scaling infrastructure decentralisation decentralization)       Posted by jermolene Filed in Uncategorized [...]</description>
		<content:encoded><![CDATA[<p>[...] The outer limits of scaling - how decentralized can your infrastructure be? « Jay by Jay Fresh Jon explores the lure of smart clients and dumb servers&#8230; (tags: jonlister scalability scaling infrastructure decentralisation decentralization)       Posted by jermolene Filed in Uncategorized [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
