The…
Up to 99.99% Availability
The…
Process monitoring and failover, typically used when deploying on bare-metal hardware
MediationZone deployed in at least 1 site/region, minimum of 2 nodes
Requires redundant disk and database storage
Configured and deployed to meet the availability target
HA Cluster Monitor 3PP Required
Cluster monitors process health via status interface
Cluster orchestrates process fail-over when issue detected
Migrated Virtual IP address
Mounts storage
Starts process on stand-by machine
Up to 99.99% Availability via VM Failover
The…
Virtual Machine (VM) monitoring and failover to alternate host, used when deploying on Virtual Machines (VMs)
VMWare vMotion, VMWare HA
AWS EC2 Auto-scaling
Etc.
MediationZone deployed in at least 1 site/region, minimum of 2 compute nodes
Requires redundant disk and database storage
Configured and deployed to meet the availability target
Process monitoring achieved by scheduling a script that starts all PICO processes not running on the local VM
Up to 99.999% Availability Geo-redundant Deployment
The…
Deployment spans at least 2 sites/regions, minimum of 2 compute nodes per site/region
Active – Active Scenarios
Independent sites/Platforms
Typically used for real-time applications
Replication requirements:
Database replication: System (NOT required), Audit (NOT required), Runtime state (optional, case dependent)
Filesystem replication: Not required
Active – Passive Scenarios
Typically used for batch applications, single Platform instance running
Replication requirements:
Database replication: System (required), Audit (optional), and Runtime state (optional)
Filesystem replication: Runtime data stored to disk
Passive site is a replica of Active site, and needs to be started when Active site goes down
VM-based High Availability Deployment
The…
System Database external to MediationZone deployment, must be setup in HA mode
System availability via:
In case of VM failure the VM is migrated to an alternate host by the virtualization environment. Required for the ControlZone, 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:
Platform process orchestrates workflow execution and failover across set of available ECs
Real-time collection workflows run as active-active across multiple ExecutionZone nodes. Traffic fail-over between nodes using:
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