anchor.diff:  The Cloud Controller also maintains records of orgs, spaces, services,
   service instances, user roles, and more.
   
  -## <a id="hm9k"></a> HM9000 ##
  +## <a id='hm9k'></a> HM9000 ##
   
   HM9000 has four core responsibilities:
   
  
positive.code: * Buildpacks
  * Droplets
  
  ## <a id="broker"></a> Service Brokers ##
  
  Applications typically depend on [services](../../services/) such as databases or
  third-party SaaS providers.
  When a developer provisions and binds a service to an application, the service
  broker for that service is responsible for providing the service instance.
  
  ## <a id="nats"></a> Message Bus ##
  
  Cloud Foundry uses [NATS](./messaging-nats.html), a lightweight
  publish-subscribe and distributed queueing messaging system, for internal
  communication between components.
  
  ## <a id="metrics"></a> Logging and Statistics ##
  
  The metrics collector gather metrics from the components.
  Operators can use this information to monitor an instance of Cloud Foundry.
  
  The application log aggregator streams application logs to developers.
  
negative.code: Containerization ensures that application instances run in isolation, get their
  fair share of resources, and are protected from noisy neighbors.
  
  ## <a id='blob'></a> Blob Store ##
  
  The blob store holds:
  
  