<?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: Technology behind kwippy and scaling</title>
	<atom:link href="http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/</link>
	<description>Giving people reasons to talk</description>
	<lastBuildDate>Tue, 06 Apr 2010 02:09:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: A Look at Kwippy And an Interview with Kwippy&#8217;s CEO &#124; CodingExperiments.com</title>
		<link>http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/comment-page-1/#comment-148</link>
		<dc:creator>A Look at Kwippy And an Interview with Kwippy&#8217;s CEO &#124; CodingExperiments.com</dc:creator>
		<pubDate>Thu, 24 Jul 2008 21:52:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/#comment-148</guid>
		<description>[...] can look at the inner details as another official Kwippy blog post gives stunning insight on the technology that Kwippy runs on. Whether or not Kwippy can scale to huge amounts of users remains to be [...]</description>
		<content:encoded><![CDATA[<p>[...] can look at the inner details as another official Kwippy blog post gives stunning insight on the technology that Kwippy runs on. Whether or not Kwippy can scale to huge amounts of users remains to be [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Attention Guys , Kwippy here ! &#171; /home/jasdeep</title>
		<link>http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/comment-page-1/#comment-116</link>
		<dc:creator>Attention Guys , Kwippy here ! &#171; /home/jasdeep</dc:creator>
		<pubDate>Wed, 09 Jul 2008 19:07:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/#comment-116</guid>
		<description>[...] django, jQuery, Nginx and memcached. They have loosely coupled the system into services, Their blog post about its architecture speaks a lot about its quality of service and proclaims its bound to scale [...]</description>
		<content:encoded><![CDATA[<p>[...] django, jQuery, Nginx and memcached. They have loosely coupled the system into services, Their blog post about its architecture speaks a lot about its quality of service and proclaims its bound to scale [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-07-08 &#171; Bloggitation</title>
		<link>http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/comment-page-1/#comment-111</link>
		<dc:creator>links for 2008-07-08 &#171; Bloggitation</dc:creator>
		<pubDate>Tue, 08 Jul 2008 00:39:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/#comment-111</guid>
		<description>[...] Technology behind kwippy and scaling (tags: python django twitter cluster 247up) [...]</description>
		<content:encoded><![CDATA[<p>[...] Technology behind kwippy and scaling (tags: python django twitter cluster 247up) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sirish</title>
		<link>http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/comment-page-1/#comment-109</link>
		<dc:creator>sirish</dc:creator>
		<pubDate>Sun, 06 Jul 2008 14:01:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/#comment-109</guid>
		<description>Hi Dipankar,

Nice post, so any plans to move your app to AWS or App Engine</description>
		<content:encoded><![CDATA[<p>Hi Dipankar,</p>
<p>Nice post, so any plans to move your app to AWS or App Engine</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tyler</title>
		<link>http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/comment-page-1/#comment-107</link>
		<dc:creator>tyler</dc:creator>
		<pubDate>Sun, 06 Jul 2008 04:38:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/#comment-107</guid>
		<description>nice post!</description>
		<content:encoded><![CDATA[<p>nice post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kwippy Offers Stability First &#124; Bwana.org</title>
		<link>http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/comment-page-1/#comment-106</link>
		<dc:creator>Kwippy Offers Stability First &#124; Bwana.org</dc:creator>
		<pubDate>Sat, 05 Jul 2008 20:06:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/#comment-106</guid>
		<description>[...] to my surprise, a new Twitter competitor arose recently called Kwippy, and they came out swinging. This blog post by Kwippy highlights their architecture and it focuses on why they will not succumb to fail-whale [...]</description>
		<content:encoded><![CDATA[<p>[...] to my surprise, a new Twitter competitor arose recently called Kwippy, and they came out swinging. This blog post by Kwippy highlights their architecture and it focuses on why they will not succumb to fail-whale [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dipankar</title>
		<link>http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/comment-page-1/#comment-104</link>
		<dc:creator>dipankar</dc:creator>
		<pubDate>Fri, 04 Jul 2008 18:19:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/#comment-104</guid>
		<description>@Shiva

Well, I don&#039;t believe what we are attempting in terms of architecture is something unique. Its a combination of a lot of learnings from other sites and articles in general. 

Its a vision which i am attempting to implement to the best of my ability, and honestly I would want more sites to run fast and never crash. The real innovation should be in how one can be useful to the user, scale issues are more of a capital / resource issue if you have the right people.

dipankar[at]kwippy.com</description>
		<content:encoded><![CDATA[<p>@Shiva</p>
<p>Well, I don&#8217;t believe what we are attempting in terms of architecture is something unique. Its a combination of a lot of learnings from other sites and articles in general. </p>
<p>Its a vision which i am attempting to implement to the best of my ability, and honestly I would want more sites to run fast and never crash. The real innovation should be in how one can be useful to the user, scale issues are more of a capital / resource issue if you have the right people.</p>
<p>dipankar[at]kwippy.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shiva</title>
		<link>http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/comment-page-1/#comment-103</link>
		<dc:creator>shiva</dc:creator>
		<pubDate>Fri, 04 Jul 2008 08:22:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/#comment-103</guid>
		<description>Dude nice post, very informative. but frankly i thought you guys would not put up something like this, since the design is where ur site has an edge, and making it public, i guess not a really sensible decision</description>
		<content:encoded><![CDATA[<p>Dude nice post, very informative. but frankly i thought you guys would not put up something like this, since the design is where ur site has an edge, and making it public, i guess not a really sensible decision</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: My first post at kwippy blog &#124; Desinerd</title>
		<link>http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/comment-page-1/#comment-102</link>
		<dc:creator>My first post at kwippy blog &#124; Desinerd</dc:creator>
		<pubDate>Thu, 03 Jul 2008 21:33:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/#comment-102</guid>
		<description>[...] http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/" rel="nofollow">http://blog.kwippy.com/2008/07/03/technology-behind-kwippy-and-scaling/</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
