anchor.diff:  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 ##
  +## <a id='blob'></a> Blob Store ##
   
   The blob store holds:
   
  
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: 
  ![Cloud Foundry Architecture](../images/cf_architecture_block.png)
  
  ## <a id='router'></a>Router ##
  
  The [router](./router.html) routes incoming traffic to the appropriate
  component, usually the Cloud Controller or a running application on a DEA node.
  
  ## <a id='uaa'></a> Authentication ##
  
  The OAuth2 server (the [UAA](./uaa.html)) and Login Server work together to
  provide identity management.
  
  ## <a id='cc'></a> Cloud Controller ##
  
  The [Cloud Controller](./cloud-controller.html) is responsible for managing the
  lifecycle of applications.
  