Architecture - Architecture

From Genesys Documentation
Revision as of 14:06, March 30, 2022 by WikiSysop (talk | contribs) (Created page with "{{ArticlePEServiceArchitecture |ServiceId=97884a5d-324e-4067-8444-8369ca96ffb8 |AdditionalTitle=Architecture |IntroductionText=The following diagram, which is intended purely...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
This is a draft page; it has not yet been published.

Learn about No results- architecture architecture

Introduction

The following diagram, which is intended purely as an example, represents a sample architecture from the Genesys SaaS offering.

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

#mintydocs_link must be called from a MintyDocs-enabled page (Draft:TLM/Current/TLMPEGuide/TempArch).

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.

Telemetry PE Architecture.png

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.