...
Scale-out architecture
Logically, the platform MediationZone platform is layered into three different zones:
- Access Zone is the layer where users access the system through a graphical interface or command line interface to perform operations and maintenance tasks.
- Control Zone hosts configurations and provides storage and a range of services that are essential to the systemthe MediationZone system.
- Execution Zone is a scale-out layer that provides processing capacity in the system. This layer contains one or several Execution Contexts and Service Contexts, which are distributed over any number of servers.
- Execution Contexts are responsible for executing and supervising workflows.
- Service Contexts host services that workflows running in Execution Contexts can share.
...
The Platform, ECs, ECSAs, and SCs run in "containers", that are installed on one or more hosts. Each installation is assigned a container name to identify it uniquely within a systema MediationZone system. One host, physical or virtual, may hold several containers, each one with a unique name and installed in separate home (MZHOME) directories.
...
- The Platform Container runs the Platform and optionally EC, ECSA and SCs. The Platform is always included in a Platform Container installation.
- Execution Containers run ECs, ECSAs and SCs. These pico instances are typically configured after the installation of the container.
Deployment Options
MediationZone has two different deployment options; Classical and Containerized. The deployments differ in the way they are installed and managed. Classical complies with the traditional 8.0 released version of MediationZone, while Containerized uses proven industry standards for virtualized scalable systems. Containerized is intended for easy installations in Amazon Web Services (AWS), and in private clouds. Also, MediationZone can be deployed in NFV environments,
...
MediationZone Picos and Service Contexts.
...
MediationZone System Component Registry (STR).
...
There are two different sets of files, depending on if installing in AWS (using EKS), or a private cloud using Kubernetes:
- AWS: Terraform infrastructure files, EKS YAML files.
...
- .