Architecture Overview
This section describes the functional architecture of Control Center (including the Control Center Agent) deployed:
-
As a single binary
-
Over a Docker infrastructure
Single Binary Architecture
The following diagram depicts the single-binary deployment option.
Browser / Control Center interaction:
-
Browser requires static files (HTML/CSS/JS/images).
-
Control Center provides the requested static files.
-
Browser initiates HTTPS and WS connections.
Control Center / Agent interaction:
-
Agent initiates connection and cluster registration in Control Center.
-
Agent initiates a bidirectional WS connection and sends the cluster info: topology, metrics, traces, etc.
-
Control Center sends commands; e.g., "get metrics requested by user."
Docker-based Architecture
The following diagram depicts the Docker deployment option.
Browser / Frontend (FE) interaction:
-
Browser requires static files (HTML/CSS/JS/images).
-
FE provides the requested static files.
-
Browser initiates HTTPS and WS connections.
Backend (BE) / Agent interaction:
-
Agent initiates connection and cluster registration in CC.
-
Agent initiates a bidirectional WS connection and sends the cluster info: topology, metrics, traces, etc.
-
BE sends commands; e.g., "get metrics requested by user."
© 2024 GridGain Systems, Inc. All Rights Reserved. Privacy Policy | Legal Notices. GridGain® is a registered trademark of GridGain Systems, Inc.
Apache, Apache Ignite, the Apache feather and the Apache Ignite logo are either registered trademarks or trademarks of The Apache Software Foundation.