anchor.diff:  
   Before and after scaling Cloud Controller API pods, you should verify that the Cloud Controller database is not overloaded. All Cloud Controller processes are backed by the same database, so heavy load on the database impacts API performance regardless of the number of Cloud Controllers deployed. Cloud Controller supports both PostgreSQL and MySQL, so there is no specific scaling guidance for the database.
   
  -Cloud Controller API pods should primarily be scaled horizontally. Scaling up the number of compute resources requested past 1 CPU is not effective. This is because Ruby's Global Interpreter Lock (GIL) limits the `cloud_controller_ng` process so that it can only effectively use a single CPU core on a multi-core machine.
  +Cloud Controller API pods should primarily be scaled horizontally. Scaling up the number of compute resources requested past one CPU is not effective. This is because Ruby's Global Interpreter Lock (GIL) limits the `cloud_controller_ng` process so that it can only effectively use a single CPU core on a multi-core machine.
   
   <p class='note'><strong>Note:</strong> Since Cloud Controller supports both PostgreSQL and MySQL external databases, there is no absolute guidance on what a healthy database looks like. In general, high database CPU utilization is a good indicator of scaling issues, but always defer to the documentation specific to your database.</p>
   
   ## <a id='cf-api-local-worker'></a> cf-api-local-worker
   
  -Colloquially known as "local workers," this container is primarily responsible for handling files uploaded to the API pods during `cf push`, such as `packages`, `droplets`, and resource matching.
  +Known as "local workers," this container is primarily responsible for handling files uploaded to the API pods during `cf push`, such as `packages`, `droplets`, and resource matching.
   
   ### When to Scale
   
  
positive.code: 
  ## <a id='cf-api-server'></a> cf-api-server
  
  The `cf-api-server` is the primary container in CAPI. It, along with `nginx`, powers the Cloud Controller API that all users of Cloud Foundry interact with. In addition to serving external clients, `cf-api-server` also provides APIs for internal components within Cloud Foundry, such as Logging and Networking subsystems.
  
  ### When to Scale
  
  
negative.code: 
  ### How to Scale
  
  Because local workers are co-located with the Cloud Controller API pod, they are scaled horizontally along with the API.
  
  ## <a id='cf-api-worker'></a> cf-api-worker
  
  Known as "generic workers" or just "workers", these pods are responsible for handling asynchronous work, batch deletes, and other periodic tasks scheduled by the `cf-api-clock`.
  
  ### When to Scale
  
  