Understanding Cloud Foundry: Architecture, Core Components, and Deployment Strategies

What Is Cloud Foundry?

Cloud Foundry is an open‑source Platform‑as‑a‑Service (PaaS) that lets developers freely choose cloud infrastructures, development frameworks, and application services. Initiated by VMware and now supported by many vendors, it streamlines development, testing, deployment, and scaling of applications on both private and public clouds.

Key Features

Supports public, private, and hybrid cloud deployments (vSphere, vCloud, AWS, OpenStack, Rackspace, Ubuntu, etc.) and offers Micro Cloud Foundry for laptop‑level PaaS.

Provides industry‑standard frameworks such as Spring for Java, Ruby on Rails, Sinatra, Node.js, Grails, Scala, Python, PHP, and more.

Includes built‑in services like RabbitMQ, PostgreSQL, MySQL, MongoDB, Redis, and allows third‑party service integration.

Scalable architecture that enables architects to validate organizational readiness for rapid cloud innovation.

Open community that encourages contributions, integration of new frameworks, services, and deployment targets.

Core Architecture

The current stable release is v2. Core components are Router, Cloud Controller, Services (Service Broker), Health Manager, DEA (Droplet Execution Agent), and the NATS messaging layer. Modules communicate via NATS or HTTP.

Router

The Router handles all incoming HTTP traffic. It distinguishes management commands from VMC/STS and user requests to applications, forwarding the latter to the DEA. The newer version replaces a Ruby‑based router with a Lua script, improving performance. Multiple routers can be deployed for load balancing.

Processes all HTTP traffic.

Updates routing tables from DEAs in real time.

Maintains distributed routing state.

Routes URLs to specific application instances.

Provides load‑balancing across app instances.

Cloud Controller

Cloud Controller is the management layer. It receives JSON commands from VMC or STS, stores data in its database, and orchestrates other components. It exposes REST APIs used by the CLI, Eclipse STS plugin, and third‑party tools for automation and integration.

Handles VMC/STS commands.

Manages users, applications, and services.

Manages cloud resources.

Packages and preprocesses applications.

Provides external REST API endpoints.

Health Manager

Health Manager collects runtime metrics from DEAs, compares them against thresholds defined in Cloud Controller, and generates alerts. It is currently less mature and resides under the Cloud Controller codebase.

Monitors health of applications and services.

Notifies Cloud Controller of anomalies.

Helps allocate resources based on usage statistics.

Service Broker (Service Component)

The Service Broker is a pluggable module that lets third‑party providers expose services (MongoDB, MySQL, PostgreSQL, RabbitMQ, Redis, vBlob, etc.) to Cloud Foundry applications. Providers can extend base classes to create custom services.

Provides an extensible layer for services.

Supports service sharing across applications.

Exposes service APIs.

Enables binding between apps and services.

DEA (Droplet Execution Agent)

DEA runs application instances inside isolated containers. Older DEA versions executed simple start/stop commands; newer versions incorporate a Warden container for CPU, memory, disk, and network isolation. DEA receives start/stop requests from Cloud Controller, fetches the appropriate droplet from NFS, runs it, and reports status to Router and Health Manager.

Executes all applications with isolation.

Monitors runtime parameters (CPU, memory, disk).

Emits status‑change alerts.

NATS Messaging

NATS is a lightweight, event‑driven publish/subscribe system that connects all Cloud Foundry components. It supports multi‑node clusters for high availability.

Provides service discovery and addressing.

Handles command and control messages.

Acts as a central communication bus.

Supports publish/subscribe semantics.

Deployment Options

Cloud Foundry can be deployed on VMware or OpenStack virtualized environments, either as a single‑node setup using dev_setup for small labs or as a large‑scale automated installation with BOSH. A lightweight Micro Cloud Foundry version runs on a developer’s laptop for quick testing.

Industry Adoption

Major telecom operators (Verizon, AT&T, NTT) and Chinese internet firms (Baidu, Yonyou, Shanda Cloud, JD.com) run Cloud Foundry in production. IBM once partnered with VMware to create an open PaaS, later evolving into the BlueMix/IBM Cloud offering. Pivotal Cloud Foundry (PCF) builds on the community edition and adds services such as Elastic Runtime, Operations Manager, and big‑data extensions (Pivotal HD, AX).