<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sun, 19 May 2013 02:13:47 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Justin Carmony's Blog: Working with Middle-Scale Websites]]></title>
      <guid>http://www.phpdeveloper.org/news/16618</guid>
      <link>http://www.phpdeveloper.org/news/16618</link>
      <description><![CDATA[<p>
In a new post <i>Justin Carmony</i> looks at what it <a href="http://www.justincarmony.com/blog/2011/07/18/working-with-middle-scale-websites/">means to me a "middle-scale website"</a> and has some recommendations for anyone working with their applications and considering things like scalability, overcompensation and finding real results through profiling.
</p>
<blockquote>
Hopefully at some point, your website is going to get a lot of traffic. Yay, you've reached your goal of getting good traffic, but it is soon followed by issues with performance and load. I like to call these the growing pains of a website. So as a web developer, I suddenly have the epiphany of "Hey, I need to scale my website!" What follows next is the biggest mistake a web developer can make: They start looking at articles on how Google scales, or maybe how Facebook manages all of their traffic. This is a mistake! To be brutally honest, you are not Google. You are not Facebook. You are not Twitter. You are a website that receives less than 0.000001% of the traffic that some of the major websites receive.
</blockquote>
<p>
He includes a "reality check" of the setup behind a popular social site, <a href="http://stackexchange.com/">StackExchange</a>, with comments from their <a href="http://blog.serverfault.com/post/stack-exchanges-architecture-in-bullet-points/">own post about their infrastructure</a>. He talks about things included in a move to "middle-scale" like adding caching, performance tweaking, moving to a multiple server model and using replication.
</p>]]></description>
      <pubDate>Thu, 21 Jul 2011 11:53:08 -0500</pubDate>
    </item>
  </channel>
</rss>
