Architecture - Architecture

Learn about No results- architecture architecture

Introduction

The suite-level architecture diagram is on the suite-level

page.

In the architecture diagram, the dotted lines from the browser (going through External Ingress and Ingress Controller) and from gws service pods (intra-cluster), to the non-tlm namespace resources, represents the connectivity required by WWE to set-up an authorized connection to the Telemetry Service. Refer to the following documentation for details about their respective connectivity:

For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level

page.

See also High availability and disaster recovery for information about high availability/disaster recovery architecture.

Architecture diagram — Connections

The numbers on the connection lines refer to the connection numbers in the table that follows the diagram. The direction of the arrows indicates where the connection is initiated (the source) and where an initiated connection connects to (the destination), from the point of view of No results as a service in the network.

Connections table

The connection numbers refer to the numbers on the connection lines in the diagram. The Source, Destination, and Connection Classification columns in the table relate to the direction of the arrows in the Connections diagram above: The source is where the connection is initiated, and the destination is where an initiated connection connects to, from the point of view of No results as a service in the network. Egress means the No results service is the source, and Ingress means the No results service is the destination. Intra-cluster means the connection is between services in the cluster.