title: Should I host Website and REST API on the same server or split?
body: <p>I have a web application that consists of Website and REST API. Should I host them on the same server or should I host them on different servers? By "server" I mean a server cluster - several servers behind load balancer.</p>
  
  <p>API is mostly inbound traffic, website - mostly outbound.</p>
  
  <p>If it matters - hosted on Rackspace and/or AWS. </p>
  
  <p>Here is what I see so far:</p>
  
  <p><b>Benefits of having Website and REST API on the same server</b></p>
  
  <ul>
  <li>Simple deployment</li>
  <li>Simple scaling - something is slow - just launch another instance</li>
  <li>Single load balancer configuration</li>
  <li>Simple monitoring</li>
  <li>Simple, simple, simple ...</li>
  <li>Effective use of full duplex network (API - inbound, website - outbound)</li>
  </ul>
  
  <p><b>Benefits of splitting</b></p>
  
  <ul>
  <li>API overload will not affect website load time</li>
  <li>Detailed monitoring (I will know which component uses resources at this moment)</li>
  </ul>
  
  <p>Any comments?</p>
  
  <p>Thank you</p>
  
  <p>Alexander</p>