Home
Architecture Overview
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.

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.
  - Parallel-MATRIXX™ Clustering
    The Parallel-MATRIXX™ protocol enables the MATRIXX Engine to run multiple logical blades simultaneously on separate blade servers while guaranteeing synchronous replication of all data across all blades.
  - Parallel-MATRIXX™ Transactions
    The Parallel-MATRIXX™ Transaction protocol enables the MATRIXX Engine processing servers to perform database reads and writes to the same data at the same time with no locking, while guaranteeing correctness of the data. The result is extremely fast, accurate processing of all transactions and the ability to scale your system to meet business needs.
  - Load Balancing
    The MATRIXX Traffic Routing Agent configured as a site-independence router (TRA-RT-(SI/DR), TRA-SI, or TRA-DR) automatically distribute messages across MATRIXX Engine based on several factors, including blade server availability, workload, and system resource usage.
  - Geographic Redundancy
    Two or three MATRIXX Engines can run in one domain and work together as a distributed system for disaster recovery. In such installations, the engines are installed in geographically-distant sites and data is replicated from one engine to another.
  - Data Quarantining
    Data quarantining protects the overall stability of the cluster from toxic data. If the MATRIXX Charging Application fails due to a low-level fault, the error is detected immediately and the database objects involved are quarantined so the bad data is not propagated across the cluster.
  - Engine Scalability and Customer Sub-Domains
    For engine scalability, a subscriber base can be segmented whereby each segment, referred to as a customer sub-domain, is processed in separate MATRIXX engine chains.
- 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 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 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.

The MATRIXX Engine uses standard clustering techniques for high availability (HA). The clusters provide processing capabilities across multiple blade servers, and allow you to remove and restore blade servers within a cluster. The MATRIXX Engine can then handle fault recovery scenarios seamlessly and in a non-system-impacting manner. Scalability is achieved by adding blade servers to clusters and by using a protocol-aware, industry standard load balancer to manage incoming data across the cluster. The load balancer can add new blade servers to the processing flow as soon as it detects they are capable of processing events.

Clustering and scalability are possible because the MATRIXX Engine supports complete data and transaction replication of all events processed by any blade server within a cluster to all other blade servers within the cluster. This is achieved without the need to block processing of an event for any reason. Resources are not locked. Different blade clusters can be processing different events from the same subscriber and the results will be correct. In addition to the speed improvements that a non-locking software architecture provides, locality of reference is not needed. For example, any blade can process an update to an open session with no additional overhead, independent of which blade processed the opening of the session.

The ability to distribute data and ensure it is 100% replicated and consistent—in real-time—across all blade servers in a cluster allows an engine to maintain full transaction processing capabilities, even in the event of a hardware or software failure.