Page Comparison

The…

Up to 99.99% Availability

...

A geo-redundant setup spans at least 2 sites/regions, with a minimum of 2 compute nodes per site/region. MediationZone can be deployed in an Active-Active or Active-Passive configuration.

...

• Filesystem: required when runtime data is stored to disk. For example File System aggregation/correlation and Duplicate UDR Detection.

• System Database: required.

• Audit: optional.

• Runtime state: optional, depending on use case.

VM-based High Availability Deployment

...

The…

...

System Database external to MediationZone deployment, must be setup in HA mode

...

, Multiple Zones

The deployment illustrated below is a single MediationZone installation spanning across several Availability Zones.

...

Recommendations:

• The System Database is handled as a separate cluster (deployed in HA mode), external to the MediationZone deployment.

• The Filesystem is mounted to all VMs if file-sharing between VMs is needed (which is common). Also, each VM has local storage embedded in the image.

MediationZone system availability:

• In case of a VM failure, the VM is migrated to an alternate host by the virtualization environment.

  Required

  This is required for the ControlZone/Platform, and is use-case dependent for

  ExecutionZone

• Filesystem mounted to all VMs if file-sharing between VMs is needed (which is common)

• Each VM has local storage embedded in the image

Workflow availability via:

an ExecutionZone.

Workflow availability:

• The ControlZone/Platform process orchestrates workflow execution and failover across a set of available ECs.

• Real-time collection workflows run as active-active across multiple ExecutionZone nodes. Traffic fail-over between nodes

  using

  uses:

  • Protocol-level failover for protocols that support it (Diameter, Radius. etc.)

  • Load balancer for all other protocols (TCP/IP, HTTP, REST, etc.)

  • Distributed VMs and ECs over multiple Availability Zones for extra redundancy