Difference between revisions of "UCS/Current/UCSPEGuide/Overview"
From Genesys Documentation
(Published) |
m (Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX") |
||
| Line 2: | Line 2: | ||
|Standalone=No | |Standalone=No | ||
|DisplayName=About Universal Contact Service (UCS) | |DisplayName=About Universal Contact Service (UCS) | ||
| − | |Context=Learn about Universal Contact Service (UCS) and how it works in Genesys | + | |Context=Learn about Universal Contact Service (UCS) and how it works in Genesys Multicloud CX private edition. |
|ComingSoon=No | |ComingSoon=No | ||
|Section={{Section | |Section={{Section | ||
Revision as of 20:31, November 9, 2021
This topic is part of the manual Universal Contact Service Private Edition Guide for version Current of Universal Contact Service.
Learn about Universal Contact Service (UCS) and how it works in Genesys Multicloud CX private edition.
Related documentation:
RSS:
Universal Contact Service (UCS) is a highly scalable, available and serviceable cloud service built with usage of PostgreSQL and Elasticsearch.
UCS covers all tenants in the specific region, having dedicated RDS per tenant. To cover N regions, it will be necessary to install N UCS in each of those regions. UCS does not support cross-region synchronization which means that only single region per tenant is supported.
UCS has an auxiliary component DataSync that can migrate data from an existing UCS 8.5 RDS for particular tenant to the newly deployed UCS RDS.
Comments or questions about this documentation? Contact us for support!