<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" media="screen" href="/styles/xslt/rss.xslt"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:c9="http://channel9.msdn.com">
<channel>
	<title>Comment Feed for Channel 9 - Windows Azure Lessons Learned: Outback Steakhouse Facebook App</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/Blogs/benriga/Azure-Lessons-Learned-Outback-Steakhouse-Facebook-App/RSS"></atom:link>
	<image>
		<url>http://ecn.channel9.msdn.com/o9/previewImages/100/510835_100x75.jpg</url>
		<title>Channel 9 - Windows Azure Lessons Learned: Outback Steakhouse Facebook App</title>
		<link></link>
	</image>
	<description>
I’m back with another episode of Azure Lessons Learned.&amp;nbsp; In this one I discuss building apps that need to be able to scale very highly very quickly.&amp;nbsp;

Jim Zimmerman, the CTO and Lead Developer for 
Thuzi, walks me through the Facebook application his team built for 
Outback Steakhouse. 
Thuzi specializes in building social media applications for large organizations to connect with their customers on sites like Facebook.&amp;nbsp; The concern with these types of applications is the possibility that the offer will go viral as it gets passed from customer
 to customer and potentially swamp the servers to the point that they are not responsive and ultimately disappoint customers.&amp;nbsp; Thuzi chose to use Windows Azure since the Windows Azure platform has ample capacity and they could scale up or down the solution
 based on the current demand of the market.&amp;nbsp; The Outback Steakhouse offer in this case was

a free Bloomin’ Onion at any of the thousands of Outback Steakhouse restaurants. 
Facebook apps don’t actually run on Facebook.&amp;nbsp; They are embedded using an iframe into a Facebook page.&amp;nbsp; The app that is running in that iframe must be hosted somewhere else.&amp;nbsp; In this case, Thuzi hosts that in Windows Azure. They actively monitor the campaign
 and turn on or off web and worker role instances as required.&amp;nbsp; In order to scale they used Windows Azure table storage and queues.&amp;nbsp; They also use SQL Azure to perform reporting and analytics on the results of the campaign.
 
</description>
	<link></link>
	<language>en</language>
	<pubDate>Thu, 23 May 2013 10:41:28 GMT</pubDate>
	<lastBuildDate>Thu, 23 May 2013 10:41:28 GMT</lastBuildDate>
	<generator>Rev9</generator>
	<item>
		<title>Re: Windows Azure Lessons Learned: Outback Steakhouse Facebook App</title>
		<description>
			<![CDATA[
<p>Thanks Ben for sharing that. &nbsp;How much up front investment do you think Azure saved Thuzi? &nbsp;Presumably the Azure architecture reduces the cost Thuzi would otherwise have had to pay in order to ensure the success of the campaign in the event it goes viral,
 as they hope.</p>
<p>posted by eniveld</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/benriga/Azure-Lessons-Learned-Outback-Steakhouse-Facebook-App#c633965927440000000</link>
		<pubDate>Wed, 16 Dec 2009 20:39:04 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/benriga/Azure-Lessons-Learned-Outback-Steakhouse-Facebook-App#c633965927440000000</guid>
		<dc:creator>eniveld</dc:creator>
	</item>
</channel>
</rss>