anchor.diff:  <%= vars.collector_singleton %>
   
   
  -## <a id='scaling'></a> Component Scaling for High Availability
  +## <a id='vert-and-horiz'></a> Vertical and Horizontal Scaling for High Availability
   
  -### <a id='vert-and-horiz'></a> Vertical and Horizontal Scaling
  -
  -You can scale platform capacity vertically by adding memory and disk, or horizontally by adding more VMs running instances of Cloud Foundry components.
  +You can scale platform capacity vertically by adding memory and disk, or horizontally by adding more VMs running instances of Cloud Foundry components. The nature of the applications you host on Cloud Foundry should determine whether you should scale vertically or horizontally.
   
   <%= image_tag("scale_cf.png", :height => "450px", :width => "475px") %>
  +
  +For more information about scaling applications and maintaining app uptime, see [Scaling an Application Using cf scale](../devguide/deploy-apps/cf-scale.html) and [Using Blue-Green Deployment to Reduce Downtime and Risk](../devguide/deploy-apps/blue-green.html).
  +
  +### <a id='vert-scaling'></a> Scale Vertically
  +
  +Scaling vertically means adding memory and disk to your component VMs.
   
   To scale vertically, ensure that you allocate and maintain enough of the following:
   
  
positive.code: 
  <%=vars.pcf_pools%>
  
  #### <a id='databases'></a> Databases
  
  For database services deployed outside Cloud Foundry, plan to leverage your infrastructure's high availability features and to configure backup and restore where possible. <%= vars.scaling_ert_db %>
  
  
negative.code: * Disk space and memory in your deployment such that if one host VM is down, all instances of apps can be placed on the remaining Host VMs.
  * Free space to handle one AZ going down if deploying in multiple AZs.
  
  ### <a id='horiz-scaling'></a> Scale Horizontally
  
  Scaling horizontally means increasing the number of VM instances dedicated to running a functional component of the system.
  
  You can horizontally scale most Cloud Foundry components to multiple instances to achieve the redundancy required for high availability. 
  
  You should also distribute the instances of multiply-scaled components across different AZs to minimize downtime during ongoing operation, product updates, and platform upgrades. If you use more than three AZs, ensure that you use an odd number of AZs.
  
  <%= vars.scaling_ert %>
  
  <%= partial vars.scale_table %>
  
  
  ## <a id='supporting-scaling'></a> Configure Support for High Availability Components
  
  This section describes the surrounding infrastructure required to support scaling component VMs for high availability.
  
  <% if vars.product_name == 'CF' %>
  <%= vars.max_in_flight_header %>
  