<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Brian Jeremy Kupetz &#124; brianjeremy.com &#124; my blog, who i am, what i do, what i've done, how to reach me, links &#187; Scalability &amp; Infrastructure</title>
	<atom:link href="http://www.brianjeremy.com/category/scalability-infrastructure/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brianjeremy.com</link>
	<description>who am i, what do i do, what have i've done?</description>
	<lastBuildDate>Sat, 24 Jul 2010 13:12:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Amazon Cloud Expands to Singapore</title>
		<link>http://www.brianjeremy.com/2010/04/30/amazon-cloud-expands-to-singapore/</link>
		<comments>http://www.brianjeremy.com/2010/04/30/amazon-cloud-expands-to-singapore/#comments</comments>
		<pubDate>Sat, 01 May 2010 00:48:41 +0000</pubDate>
		<dc:creator>brian</dc:creator>
				<category><![CDATA[Cloud Computing]]></category>
		<category><![CDATA[Scalability & Infrastructure]]></category>

		<guid isPermaLink="false">http://www.brianjeremy.com/?p=366</guid>
		<description><![CDATA[Amazon has taken the first steps to expand it&#8217;s operations outside the US and Europe by unveiled a new data center in Singapore.  This entry to the Asia Pacific region is significant both to a potential new customer base and existing clientele who will reap the benefits of having the opportunity to have a [...]]]></description>
			<content:encoded><![CDATA[<p>Amazon has taken the first steps to expand it&#8217;s operations outside the US and Europe by unveiled a new data center in Singapore.  This entry to the Asia Pacific region is significant both to a potential new customer base and existing clientele who will reap the benefits of having the opportunity to have a more global infrastructure with less latency in Asia Pacific.</p>
<p>With the addition of the new data center in Singapore, Amazon has updated their list of current Amazon EC2 public address ranges:<br />
<code></p>
<p><b><u>US East (Northern Virginia)</u></b><br />
216.182.224.0/20 (216.182.224.0 - 216.182.239.255)<br />
72.44.32.0/19 (72.44.32.0 - 72.44.63.255)<br />
67.202.0.0/18 (67.202.0.0 - 67.202.63.255)<br />
75.101.128.0/17 (75.101.128.0 - 75.101.255.255)<br />
174.129.0.0/16 (174.129.0.0 - 174.129.255.255)<br />
204.236.192.0/18 (204.236.192.0 - 204.236.255.255)<br />
184.73.0.0/16 (184.73.0.0 – 184.73.255.255)<br />
<i>184.72.128.0/17 (184.72.128.0 - 184.72.255.255)*</i></p>
<p><b><u>US West (Northern California)</u></b><br />
204.236.128.0/18 (216.236.128.0 - 216.236.191.255)<br />
184.72.0.0/18 (184.72.0.0 – 184.72.63.255)</p>
<p><b><u>EU (Ireland)</u></b><br />
79.125.0.0/17 (79.125.0.0 - 79.125.127.255)</p>
<p><b><u>Asia Pacific (Singapore)</u></b><br />
<i>175.41.128.0/18 (175.41.128.0 - 175.41.191.255)*</i></p>
<p></code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.brianjeremy.com/2010/04/30/amazon-cloud-expands-to-singapore/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>House Website Can&#8217;t Withstand Failed Buyout</title>
		<link>http://www.brianjeremy.com/2008/09/29/house-website-cant-withstand-failed-buyout/</link>
		<comments>http://www.brianjeremy.com/2008/09/29/house-website-cant-withstand-failed-buyout/#comments</comments>
		<pubDate>Tue, 30 Sep 2008 00:28:29 +0000</pubDate>
		<dc:creator>brian</dc:creator>
				<category><![CDATA[Application Servers]]></category>
		<category><![CDATA[Scalability & Infrastructure]]></category>
		<category><![CDATA[Web Servers]]></category>

		<guid isPermaLink="false">http://www.brianjeremy.com/?p=277</guid>
		<description><![CDATA[It seems there are so many American&#8217;s that aren&#8217;t happy about the failed $700 Billion buyout plan that the www.house.gov website is taking two minutes to load [in some cases not loading at all].  I&#8217;m not all that happy with politicians these days, but I don&#8217;t really feel that sending them an email through the [...]]]></description>
			<content:encoded><![CDATA[<p>It seems there are so many American&#8217;s that aren&#8217;t happy about the failed $700 Billion buyout plan that the <a title="www.house.gov" href="http://www.house.gov" target="_blank">www.house.gov</a> website is taking two minutes to load [in some cases not loading at all].  I&#8217;m not all that happy with politicians these days, but I don&#8217;t really feel that sending them an email through the house.gov website is really going to result in better policy.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.brianjeremy.com/2008/09/29/house-website-cant-withstand-failed-buyout/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Safari 3.0 Tips for Developers</title>
		<link>http://www.brianjeremy.com/2008/02/11/safari-30-tips-for-developers/</link>
		<comments>http://www.brianjeremy.com/2008/02/11/safari-30-tips-for-developers/#comments</comments>
		<pubDate>Mon, 11 Feb 2008 15:49:50 +0000</pubDate>
		<dc:creator>brian</dc:creator>
				<category><![CDATA[HTML Development]]></category>
		<category><![CDATA[Scalability & Infrastructure]]></category>
		<category><![CDATA[Web Servers]]></category>

		<guid isPermaLink="false">http://www.brianjeremy.com/2008/02/11/safari-30-tips-for-developers/</guid>
		<description><![CDATA[If you have upgraded from the Apple Safari version 2.0 web browser to 3.0 here are two quick tips that developers and Q&#38;A folks might find useful.  The first tip is to turn on the built-in Web Developers Kit which is similar to the Firefox Firebug plug-in.  Once you activate it (instructions are [...]]]></description>
			<content:encoded><![CDATA[<p>If you have upgraded from the <a href="http://www.apple.com" title="Apple" target="_blank">Apple</a> Safari version 2.0 web browser to 3.0 here are two quick tips that developers and Q&amp;A folks might find useful.  The first tip is to turn on the built-in Web Developers Kit which is similar to the Firefox Firebug plug-in.  Once you activate it (instructions are below) you can launch it by right clicking the browser window and selecting &#8220;Inspect Element.&#8221;  The other tip changes the page loading progress bar (the standard filling of the address bar from left to write in blue) to a simple pie chart that fills clockwise indicating page load completion.  If you wish to deactivate either of these features you can  use the same instructions replacing the &#8220;-bool true&#8221; with &#8220;-bool false&#8221;</p>

<div class="wp_syntax"><div class="code"><pre class="html" style="font-family:monospace;">Finder-&gt;Applications-&gt;Utilities-&gt;Terminal
&nbsp;
defaults write com.apple.Safari DebugUsePieProgressIndicator -bool true
defaults write com.apple.Safari WebKitDeveloperExtras -bool true</pre></div></div>

<p><!-- WebKitDeveloperExtras --></p>
]]></content:encoded>
			<wfw:commentRss>http://www.brianjeremy.com/2008/02/11/safari-30-tips-for-developers/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Yahoo.com&#8217;s YSlow Documentation Lacking</title>
		<link>http://www.brianjeremy.com/2008/02/03/yahoocoms-yslow-documentation-lacking/</link>
		<comments>http://www.brianjeremy.com/2008/02/03/yahoocoms-yslow-documentation-lacking/#comments</comments>
		<pubDate>Sun, 03 Feb 2008 22:01:18 +0000</pubDate>
		<dc:creator>brian</dc:creator>
				<category><![CDATA[Application Servers]]></category>
		<category><![CDATA[Scalability & Infrastructure]]></category>
		<category><![CDATA[Web Servers]]></category>

		<guid isPermaLink="false">http://www.brianjeremy.com/2008/02/03/yahoocoms-yslow-documentation-lacking/</guid>
		<description><![CDATA[I&#8217;ve recently been working on performance tuning a set of application servers for optimal performance of a high volume website.   YSlow is a Firefox Add-on that works in conjunction with the Firebug add-on that is intended to help you analyze and understand performance based on Yahoo.com&#8217;s rules of &#8220;High Performance Websites.&#8221;
If you work [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve recently been working on performance tuning a set of application servers for optimal performance of a high volume website.   <a href="https://addons.mozilla.org/en-US/firefox/addon/5369" title="Firefox - YSlow" target="_blank">YSlow</a> is a <a href="http://www.mozilla.com/en-US/firefox/" title="Firefox" target="_blank">Firefox</a> Add-on that works in conjunction with the <a href="https://addons.mozilla.org/en-US/firefox/addon/1843" title="Firefox - Firebug - Add on" target="_blank">Firebug</a> add-on that is intended to help you analyze and understand performance based on Yahoo.com&#8217;s rules of &#8220;High Performance Websites.&#8221;</p>
<p>If you work with the YSlow tool in a development environment you likely aren&#8217;t going to be using a Content Delivery Network (CDN) such as <a href="http://www.akamai.com" title="Akamai" target="_blank">Akamai</a> or <a href="http://www.limelightnetworks.com/" title="CDN - Limelight Networks" target="_blank">Limelight Networks</a>.   Thus, you get a lower optimization score when testing.  This can obviously be misleading, and there is a work around documented in Yahoo&#8217;s <a href="http://developer.yahoo.com/yslow/faq.html#faq_cdn" title="Yahoo YSlow FAQ" target="_blank">YSlow FAQ</a>.  The problem is that the documentation explains the work around must be configured via: &#8220;Go to <code>about:config</code> in Firefox. You&#8217;ll see the current list of preferences.&#8221;  The issue/confusion is that many people don&#8217;t realize that &#8220;<code>about:config</code>&#8221; isn&#8217;t an option of your browser preferences, or preferences of your plug-ins.  You must type &#8220;<code>about:config</code>&#8221; into the address bar of your browser to pull up these configuration parameters.</p>
<p>The YSlow plug-in itself is very useful.  However, the documentation seems a bit lacking so hopefully I am able to save others who attempt to configure it some valuable time.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.brianjeremy.com/2008/02/03/yahoocoms-yslow-documentation-lacking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Upcoming Presentations, mark your calendar.</title>
		<link>http://www.brianjeremy.com/2007/11/08/upcoming-presentations-mark-your-calendars/</link>
		<comments>http://www.brianjeremy.com/2007/11/08/upcoming-presentations-mark-your-calendars/#comments</comments>
		<pubDate>Thu, 08 Nov 2007 14:00:51 +0000</pubDate>
		<dc:creator>brian</dc:creator>
				<category><![CDATA[Grails]]></category>
		<category><![CDATA[Groovy]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Scalability & Infrastructure]]></category>
		<category><![CDATA[Startups]]></category>

		<guid isPermaLink="false">http://www.brianjeremy.com/2007/11/08/upcoming-presentations-mark-your-calendars/</guid>
		<description><![CDATA[I will be doing two presentations the second week of January.  The first one will be Jan. 9th in El Segundo for the Los Angeles Java User Group (LAJUG) and the second one will be Jan 11th in Irvine for the Orange County Java User Group (OCJUG).  Both presentations will be on the [...]]]></description>
			<content:encoded><![CDATA[<p>I will be doing two presentations the second week of January.  The first one will be Jan. 9th in El Segundo for the Los Angeles Java User Group (<a href="http://www.lajug.org" title="Los Angeles Java User Group">LAJUG</a>) and the second one will be Jan 11th in Irvine for the Orange County Java User Group (<a href="http://www.ocjug.org/" title="Orange County Java User Group" target="_blank">OCJUG</a>).  Both presentations will be on the topic of Groovy and Grails and the experience of using emerging technologies in  a &#8220;Web 2.0&#8243; Startup.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.brianjeremy.com/2007/11/08/upcoming-presentations-mark-your-calendars/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Scalability, others care too!</title>
		<link>http://www.brianjeremy.com/2007/09/05/scalability-others-care-too/</link>
		<comments>http://www.brianjeremy.com/2007/09/05/scalability-others-care-too/#comments</comments>
		<pubDate>Wed, 05 Sep 2007 16:15:10 +0000</pubDate>
		<dc:creator>brian</dc:creator>
				<category><![CDATA[Scalability & Infrastructure]]></category>

		<guid isPermaLink="false">http://www.brianjeremy.com/2007/09/05/scalability-others-care-too/</guid>
		<description><![CDATA[So, It&#8217;s not the greatest source of information in the world, but its definitely a resource.  If you are or have been working on a highly scalable project as I have I&#8217;d suggest a visit to HighScalability.com.  There are some real world examples of web/server architectures for large commonly known sites such as [...]]]></description>
			<content:encoded><![CDATA[<p>So, It&#8217;s not the greatest source of information in the world, but its definitely a resource.  If you are or have been working on a highly scalable project as I have I&#8217;d suggest a visit to <a href="http://www.highscalability.com/" title="highscalability.com" target="_blank">HighScalability.com</a>.  There are some real world examples of web/server architectures for large commonly known sites such as Amazon, Digg, YouTube and so forth.  It&#8217;s hard to say how accurate the information is, but its always nice to know what others are up too.  I&#8217;m from the school of each problem has its own solution, but if you are in the field visit the site, read a few pages and share your thoughts.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.brianjeremy.com/2007/09/05/scalability-others-care-too/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
