Architecture - Cross-region

From Genesys Documentation
Jump to: navigation, search
This topic is part of the manual Voice Microservices Private Edition Guide for version Current of Voice Microservices.

Learn about Voice Microservices- cross-region architecture

Introduction

The following diagram shows an example of cross-region architecture for Voice Microservices.

For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level Architecture 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 Voice Microservices as a service in the network.

Voicemcs voice k8s crossregion highlevel architecture diagram.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 Voice Microservices as a service in the network. Egress means the Voice Microservices service is the source, and Ingress means the Voice Microservices service is the destination. Intra-cluster means the connection is between services in the cluster.

Comments or questions about this documentation? Contact us for support!