The differences between implementing MATRIXX Digital Commerce on bare-metal, and on a sole-tenant Google Cloud Platform (GCP) include the use of Google
load balancers, a MATRIXX TRA-PROC setting, and the use of only one MATRIXX Engine
publishing server. The MATRIXX on GCP network diagram provided here will help you understand
the networking components required.
Note: This documentation refers to all Google Load Balancers in general by the acronym
"GLBs." It also refers to "internal GLBs" ("ILBs") and "external GLBs" when that
distinction is necessary.
The architectural differences between the bare-metal version MATRIXX Digital Commerce and GCP version include:
Internal Google Load Balancers
(ILBs) load balance of traffic among the MATRIXX Engines, instead of the
MATRIXX TRA-SI/DRs. In addition, the ILBs handle VPN and client traffic
entering the MATRIXX Digital Commerce implementation. However, even though the ILBs provide these services, it
is still necessary to configure the TRA VIPs with the option that makes them
non-floating (floating="false").
The MATRIXX TRA-PROC is not co-located on the MATRIXX Engine in GCP deployments. Instead, it is installed and configured as a separate
compute instance (node).
Only one MATRIXX Engine publishing blade is required in GCP deployments. GCP itself provides the
necessary redundancy and can restart the publishing blade efficiently to
supply the HA features required.
Sole-tenant Node Requirement
MATRIXX Digital Commerce must be implemented on sole-tenant nodes in the Google Cloud Platform. For
information on creating sole tenant nodes, see the Google Cloud documentation.
MATRIXX Digital Commerce on GCP Network Configuration
Figure 1 shows an
example network configuration for MATRIXX Digital Commerce in a GCP environment. For high availability, MATRIXX recommends that you use two
different Google Cloud zones, although this is not shown in the diagram. All IP
addresses in this diagram are examples. The various MATRIXX servers in blue boxes
are implemented as Google processing virtual machines (VMs). The darker blue boxes
represent Google Cloud persistent disk block storage. The green
rectangles show Google Cloud services. The Google services shown
are Google Load Balancers. Figure 1. MATRIXX Digital Commerce on GCP
Note: You must disable the GCP VM snapshot feature before installing and starting a MATRIXX Digital Commerce implementation on the GCP. The snapshot feature interferes with MATRIXX disk I/O
throughput, which may cause it to shut down unexpectedly.
Notes on this diagram:
The individual components of the Business API Gateway are aggregated instead of being pictured separately.
To support voice traffic, you would also need to
add redundant Call Control Framework (CCF) Network Enabler
VMs to this network.
The sections in this chapter explain the tasks required to implement MATRIXX Digital Commerce on GCP.
