<commit_before>---
title: Cloud Foundry Components
---

Cloud Foundry components include a self-service application execution engine, an
automation engine for application deployment and lifecycle management, and a
scriptable command line interface (CLI), as well as integration with development
tools to ease deployment processes.
Cloud Foundry has an open architecture that includes a buildpack mechanism for
adding frameworks, an application services interface, and a cloud provider
interface.

Refer to the descriptions below for more information about Cloud Foundry
components.
Some descriptions include links to more detailed documentation.

![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.
When a developer pushes an application to Cloud Foundry, she is targeting the
Cloud Controller.
The Cloud Controller then stores the raw application bits, creates a record to
track the application metadata, and directs a DEA node to stage and run the
application.
The Cloud Controller also maintains records of orgs, spaces, services,<commit_msg>fix path to images in architecture/index.html<commit_after>---
title: Cloud Foundry Components
---

Cloud Foundry components include a self-service application execution engine, an
automation engine for application deployment and lifecycle management, and a
scriptable command line interface (CLI), as well as integration with development
tools to ease deployment processes.
Cloud Foundry has an open architecture that includes a buildpack mechanism for
adding frameworks, an application services interface, and a cloud provider
interface.

Refer to the descriptions below for more information about Cloud Foundry
components.
Some descriptions include links to more detailed documentation.

![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.
When a developer pushes an application to Cloud Foundry, she is targeting the
Cloud Controller.
The Cloud Controller then stores the raw application bits, creates a record to
track the application metadata, and directs a DEA node to stage and run the
application.
The Cloud Controller also maintains records of orgs, spaces, services,
{'fraction_non_alphanumeric': 0.0669671603348358, 'fraction_numerical': 0.000643915003219575, 'mean_word_length': 5.2894736842105265, 'pattern_counts': {'":': 0, '<': 15, '<?xml version=': 0, '>': 15, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7461794', 'n_tokens_mistral': 730, 'n_tokens_neox': 713, 'n_words': 394}