> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/tools/enterprise/control-center/admin-guide/architecture-overview.md).

# Architecture Overview

The functional architecture of GridGain Control Center and the Control Center Agent, for single-binary and Docker deployments.

This section describes the functional architecture of Control Center (including the Control Center Agent) deployed:

* As a single binary
* Over a Docker infrastructure

{% hint style="info" %}
Cluster must have open egress on `TCP:8080`. Control Center must have open ingress for `TCP:8080`. If the cluster is SSL-enabled, change `8080` to `443`.
{% endhint %}

## Single Binary Architecture

The following diagram depicts the single-binary deployment option.

![Binary deployment](https://2850516351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkuTXWg0NDbRx6XUeYpGD%2Fuploads%2Fgit-blob-1dc9c014063400dc9e0ab6c7bb2d620aa3152531%2Fcc-admin-guide-binary.png?alt=media)

Browser / Control Center interaction:

1. Browser requires static files (HTML/CSS/JS/images).
2. Control Center provides the requested static files.
3. Browser initiates HTTPS and WS connections.

Control Center / Agent interaction:

1. Agent initiates connection and cluster registration in Control Center.
2. Agent initiates a bidirectional WS connection and sends the cluster info: topology, metrics, traces, etc.
3. Control Center sends commands; e.g., "get metrics requested by user."

## Docker-based Architecture

The following diagram depicts the Docker deployment option.

![Docker deployment](https://2850516351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkuTXWg0NDbRx6XUeYpGD%2Fuploads%2Fgit-blob-fa7723dd0813027bdb5479462dabfec40800d8eb%2Fcc-admin-guide-docker.png?alt=media)

Browser / Frontend (FE) interaction:

1. Browser requires static files (HTML/CSS/JS/images).
2. FE provides the requested static files.
3. Browser initiates HTTPS and WS connections.

Backend (BE) / Agent interaction:

1. Agent initiates connection and cluster registration in CC.
2. Agent initiates a bidirectional WS connection and sends the cluster info: topology, metrics, traces, etc.
3. BE sends commands; e.g., "get metrics requested by user."