Home
Architecture Overview
MATRIXX Disaster Recovery (DR)
MATRIXX Digital Commerce is designed to handle a range of possible disasters, including natural, technical, and human hazards. No decision making required during a disaster because the active engine is configured to automatically fail over to a standby engine that has the same built-in reliability and nearly-the-same transaction data.

Welcome
Release Notes
Architecture Overview
- About the Architecture Overview
  Architecture Overview provides information about the MATRIXX Digital Commerce™ functionality.
- MATRIXX Digital Commerce Introduction
  MATRIXX Digital Commerce is a real-time, transactional system designed to more efficiently support the growing volume and complexity of services that require real-time processing.
- MATRIXX Digital Commerce Overview
  MATRIXX Digital Commerce core components receive network messages, perform event-transaction processing, archive data needed for engine high-availability or disaster-recovery purposes, and publish or store event-transaction data for use by other systems.
- Virtualization and Cloud Deployment
  MATRIXX Digital Commerce is designed for deployment in public, private, or hybrid clouds as an alternative to on-premise (bare metal) hardware deployment.
- MATRIXX Engine Architecture
  A MATRIXX Engine environment can include an active, a standby, and (optionally) a second standby engine. A MATRIXX Engine must have at least one backup engine, referred to as the standby engine or high-availability (HA) peer. A MATRIXX Engine and its configured standby peers together form an engine chain, which work together for disaster-recovery purposes. Should one engine fail, one of the standby(s) take over. For information about what happens when an active engine fails, see the discussion about disaster recovery.
- MATRIXX 5G Interface (SBA Gateway)
  MATRIXX Digital Commerce MATRIXX SBA Gateway provides a 5G interface for a Charging Server (OCS) and converged charging service (CCS) (including authorization and authentication), and is the consumer for Nchf_ConvergedCharging and Nchf_SpendingLimitControl for spending limit reporting. It is delivered as a Docker image or RPM file.
- MATRIXX Business API Gateway
  MATRIXX Digital Commerce Business API Gateway includes the RS (REST Services) Gateway and Gateway Proxy that translate REST and Java communication into the MDCs that the other MATRIXX components use to communicate. This gateway is implemented as a high-availability (HA) pair for reliability.
- MATRIXX Traffic Routing Agent
  The MATRIXX Digital Commerce Traffic Routing Agents (TRAs) load-balance and route traffic among the MATRIXX Digital Commerce components and provide high availability (HA) protection. Depending on their function, the TRAs can also load balance traffic and serve as a Diameter peer. In addition to HA protection, TRAs also provide a single virtual IP address point of access for BSS systems and network nodes to send network traffic to.
- MATRIXX Route Cache Controller
  In a MATRIXX environment where multiple customer sub-domains are implemented, the Route Cache (a database) is required in the traffic-routing layer.
- MATRIXX SIGTRAN Network Enabler Components
  The MATRIXX Digital Commerce SIGTRAN Network Enabler is a MATRIXX service that load balances TCAP messages across the MATRIXX Engine processing blades, which provides charging and balance control operations. In terms of RFC4666 (M3UA), each Network Enabler acts as a signaling gateway process (SGP) and the MATRIXX services on the processing blades act as application server processes (ASPs).
- MATRIXX Digital Commerce Applications
  MATRIXX Digital Commerce is comprised of several applications that run seamlessly on one MATRIXX Engine to provide a total solution.
- MATRIXX Business API SDK
  The Business API SDK is a framework that includes a set of tools to manage, customize and extend RS Gateway for your business needs.
- MATRIXX Event Streaming Framework
  Used in environments in which the MATRIXX Event Streaming feature is enabled, or where event loading with MEFv2s is used, the Event Streaming Framework is a gateway that connects a MATRIXX Engine cluster to external systems that consume the event streams.
- MATRIXX Engine Software Topology
  The MATRIXX™ Real-Time Engine software consists of a set of core software servers and one or more business modules. This is called a MATRIXX server (blade).
- MATRIXX Engine Data Model
  The MATRIXX Engine data model is object based. All objects are defined in XML, making them easily extendable and the in-memory databases highly configurable.
- MATRIXX Engine Modules
  The MATRIXX Engine modules run on top of the MATRIXX Engine and contain the business logic for MATRIXX Telco applications.
- MATRIXX Digital Commerce Security
  MATRIXX Digital Commerce should be deployed within a secure area of a carrier's network. Servers should have limited access points for event processing, business support systems, maintenance and monitoring, and local access.
- MATRIXX Engine High Availability and Scalability
  MATRIXX uses a combination of industry standard clustering techniques as well as a proprietary technique to achieve both high availability and high scalability within the MATRIXX Engine.
- MATRIXX Disaster Recovery (DR)
  MATRIXX Digital Commerce is designed to handle a range of possible disasters, including natural, technical, and human hazards. No decision making required during a disaster because the active engine is configured to automatically fail over to a standby engine that has the same built-in reliability and nearly-the-same transaction data.
  - MATRIXX Traffic Routing Agent DR Features
    MATRIXX Traffic Routing Agent provides an isolation layer between the network and the MATRIXX Engines configured as a Disaster Recovery (DR) group. It is installed on a server located between the network and the MATRIXX Engine DR group, and provides a single virtual IP address to which the network sends traffic—independent of which engine is active at any given time.
  - Transaction Replay
    Transactions are replayed first from all the MATRIXX Engine processing blades on an engine, to the active publishing blade on that engine. This creates the first redundant set of transaction events.
  - Total System Failure Resolution
    MATRIXX Engine handles fault recovery scenarios in a seamless and non-system-impacting manner in most situations. When the ACTIVE cluster fails, the Cluster Manager initiates a fail-over operation to the STANDBY cluster node and the Traffic Routing Agent switches the incoming network traffic automatically to that cluster, which becomes the ACTIVE processing cluster, preventing a service outage. However, if an engine fails and the peer engine cluster loses quorum due to the loss of one or more blades, shutting down the peer engine could result in a service outage.
MATRIXX Cloud Native Installation and Configuration
MATRIXX Cloud Native Integration
Implementing MATRIXX in a Cloud
Installation and Configuration
MATRIXX Digital Commerce Upgrade
MATRIXX Security
MATRIXX Engine Administration
MATRIXX Web App Administration
MATRIXX Engine Integration
Call Control Framework Integration
MATRIXX Diameter Integration
MATRIXX 5G Integration
MATRIXX Monitoring and Logging
Pricing and Rating
MATRIXX Pay Now
MATRIXX Policy
MATRIXX Event Streaming
Subscriber Management
Subscriber Management (SubMan) API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
Third-Party Licenses
Glossary

MATRIXX Disaster Recovery (DR)

MATRIXX Digital Commerce is designed to handle a range of possible disasters, including natural, technical, and human hazards. No decision making required during a disaster because the active engine is configured to automatically fail over to a standby engine that has the same built-in reliability and nearly-the-same transaction data.

The redundant architecture and fault detection capabilities provide rapid fail-over capabilities for a blade, a cluster, and an engine, so processing is not disrupted and the risk of any delays is minimized. Specific steps to recover from any failed component of the system are handled automatically. In addition, the replaying of transactions on a standby engines and the creation of database checkpoints guarantee data consistency and keep the standby engines in sync with the active engine.

The processing and publishing clusters in the primary and secondary MATRIXX Engines are deployed in geographically-distributed DR pairs to provide high-availability and inter-cluster disaster recovery. The two clusters in the DR pair are referred to as the HA peer clusters, and have an ACTIVE-STANDBY HA mode. Only one cluster in the HA pair can actively process network traffic. This is the processing cluster in the active engine. If the Cluster Manager running on this engine detects problems with either the processing or publishing clusters it shuts down the processing cluster, which gracefully fails over the engine and activates the secondary engine. For details, see the discussion about conditions that trigger a failover in MATRIXX Engine Administration.

Note: Regardless of cluster status, the last MATRIXX Engine running in a MATRIXX Digital Commerce environment always remains running to prevent a processing outtage.

The active/standby states of the clusters in a DR pair are dynamic in that they can change as a result of a cluster failure (failover), an administrative shutdown of the active cluster, or a forced switch-over of these states by using a command line interface (CLI).