anchor.diff:  
   ### How to Scale
   
  -Both of these pods are singletons, so extra instances are for failover HA rather than scalability. Performance issues are likely due to database overloading.
  -
  +Both of these pods are singletons, so extra instances are for failover high availability rather than scalability. Performance issues are likely due to database overloading.
  
positive.code: 
  ### How to Scale
  
  Because local workers are colocated with the Cloud Controller API pod, they are scaled horizontally along with the API.
  
  ## <a id='cf-api-worker'></a> cf-api-worker
  
  Colloquially 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
  
  
negative.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
  
  