<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Web Servers on Justin Carmony</title>
		<link>https://www.justincarmony.com/tags/web-servers/</link>
		<description>Recent content in Web Servers on Justin Carmony</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Tue, 25 Oct 2011 03:50:59 +0000</lastBuildDate>
		
			<atom:link href="https://www.justincarmony.com/tags/web-servers/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Setting Up Nginx &amp; PHP-FPM on Ubuntu 10.04</title>
				<link>https://www.justincarmony.com/2011/10/25/setting-up-nginx-php-fpm-on-ubuntu-10-04/</link>
				<pubDate>Tue, 25 Oct 2011 03:50:59 +0000</pubDate>
				<guid>https://www.justincarmony.com/2011/10/25/setting-up-nginx-php-fpm-on-ubuntu-10-04/</guid>
				<description>&lt;p&gt;This is another wonderful setup that I&amp;rsquo;ve found myself using rather than the traditional Apache &amp;amp; mod_php setup.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-nginx&#34;&gt;What is Nginx?&lt;/h2&gt;&#xA;&lt;p&gt;Nginx (pronounced engine-x) is a fast, powerful, lightweight web server. I won&amp;rsquo;t go into the theory under-the-hood, but it&amp;rsquo;s focus is high concurrency with low memory usage. So while Apache is more robust in supporting many different features, nginx focuses on handling the important features very quickly. I still use Apache internally for our SVN &amp;amp; Trac web server. Heck, even at this time I&amp;rsquo;m using Apache to host this blog. However, Dating DNA, Clipish, CEVO, Alienware Arena, and some other high traffic sites/apis use nginx.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Using Cloud Files w/ CDN for Clipish Library</title>
				<link>https://www.justincarmony.com/2010/12/30/cloudfiles-with-cdn-hosts-clipish-library/</link>
				<pubDate>Thu, 30 Dec 2010 22:19:40 +0000</pubDate>
				<guid>https://www.justincarmony.com/2010/12/30/cloudfiles-with-cdn-hosts-clipish-library/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://www.justincarmony.com/images/wp/2010/12/rackspace_logo.gif&#34;&gt;&lt;img src=&#34;https://www.justincarmony.com/images/2010/12/rackspace_logo-150x150.gif&#34; alt=&#34;&#34; title=&#34;rackspace_logo&#34;&gt;&lt;/a&gt;Over the last two days we&amp;rsquo;ve moved our &lt;a href=&#34;http://www.clipish.net/&#34;&gt;Clipish&lt;/a&gt; Library from serving the files locally on our web server to &lt;a href=&#34;http://www.rackspacecloud.com/cloud_hosting_products/files/&#34;&gt;Rackspace&amp;rsquo;s Cloud Files&lt;/a&gt; service. It is similar to &lt;a href=&#34;http://aws.amazon.com/s3/&#34;&gt;Amazon S3,&lt;/a&gt; however since we were already using Rackspace Cloud Servers, we thought it would be easier to just keep it all under the same roof. The actual changes in code for using Cloud Files only took about 2 hours, but I had to write a script to loop through our entire library and populate Cloud Files with our current library. What is great is in the future when we add items, our code will automatically add files to Cloud Files via their API. Here is our network graph after switching (Item #3):&lt;/p&gt;</description>
			</item>
			<item>
				<title>Sharing Sessions Across Multiple Servers With Memcache</title>
				<link>https://www.justincarmony.com/2010/09/15/sharing-sessions-across-multiple-servers-with-memcache/</link>
				<pubDate>Wed, 15 Sep 2010 08:52:15 +0000</pubDate>
				<guid>https://www.justincarmony.com/2010/09/15/sharing-sessions-across-multiple-servers-with-memcache/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://www.justincarmony.com/images/wp/2010/09/memcached-logo-200x152.png&#34;&gt;&lt;img src=&#34;https://www.justincarmony.com/images/2010/09/memcached-logo-200x152-150x150.png&#34; alt=&#34;&#34; title=&#34;memcached-logo-200x152&#34;&gt;&lt;/a&gt;These last few days have been full of quickly implementing things I&amp;rsquo;ve only read about, but hadn&amp;rsquo;t done for myself.&lt;/p&gt;&#xA;&lt;p&gt;One situation was looking at splitting web traffic across multiple servers. In our case, we had only 2% of our website that would spike and increase our load by %1000 percent (I&amp;rsquo;m not joking) for a short period of time. So instead of doing traditional load balancing, we opted for routing specific functions to a custom subdomain that would run on another server. That way if the thousands of crazy video game players (you know who you are), slam the servers trying to get a cool skin for their online avatar, it would only take down that one section.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
