title: PHP code organization for deployment to our servers
body: <p>We just got new servers for our new system and I want to know what I should do to make my new code as efficient as possible, and how to organize it.</p>
  <p>I want a good solution so I don't have to reorganize it one year from now on (for example) and I want the best practices and techniques to make sure my code will survive long enough to avoid redesigning it later. <strong>no framework use here</strong></p>
  <p>Here's my new environment:</p>
  <ul>
  <li>8 web servers LAMP (Apache 2, PHP 5.3.5, CentOS 5) - (<a href="https://en.wikipedia.org/wiki/Xeon" rel="nofollow noreferrer">Xeon</a> <a href="https://en.wikipedia.org/wiki/List_of_Intel_Nehalem-based_Xeon_microprocessors#ark48768" rel="nofollow noreferrer">E5645</a>, 32 GB RAM, <a href="https://en.wikipedia.org/wiki/Nested_RAID_levels#RAID_10_(RAID_1+0)" rel="nofollow noreferrer">RAID 10</a> 1 TB 15k RPM) - one load balancer to manage them</li>
  <li>12 database MySQL 5.5 servers (same as above) with replication (four masters and eight slaves)</li>
  <li>one <a href="https://en.wikipedia.org/wiki/Apache_Subversion" rel="nofollow noreferrer">SVN</a> server (an old server we use)</li>
  </ul>
  <p>My idea was to mirror them (the web servers) and then push the code from the SVN to all servers. Is this good?</p>