Line 15: | Line 15: | ||
==Data Services== | ==Data Services== | ||
+ | GWS v9 uses multiple data sources to store its data. | ||
'''PostgreSQL''' | '''PostgreSQL''' | ||
− | * | + | * GWS-specific configuration details (contact center & environment) are stored. |
− | + | * Data stored in PostgreSQL is persistent. | |
− | * PostgreSQL | ||
− | |||
'''Redis''' | '''Redis''' | ||
− | * Redis is used for system-wide caching, where concurrent requests are served from | + | * Redis is used for system-wide caching, where concurrent requests are served from Cache. |
− | * Redis is | + | * Data stored in Redis is not persistent. It is always runtime. |
− | |||
'''Elastic Search''' | '''Elastic Search''' | ||
− | + | * Elastic Search searchable data from the Configuration Server which used by WWE and other services. | |
− | * Elastic Search | + | * Elastic Search used to store statistical information for WWE related functionality. |
− | * | + | * Data stored in Elastic Search is not persistent. It is always runtime. |
− | |||
− | * | ||
==CometD== | ==CometD== |
Revision as of 07:01, March 24, 2020
Architecture of Web Services and Applications
Description of the preceding diagram
Genesys Web Services (GWS) is an application cluster composed of several microservices that run together. GWS runs on multiple Containers that are categorized as below:
- Data Services: These services use multiple data source (third-party databases) to store GWS data. These databases should be maintained by customers.
- Platform Services: These services are used to connect to Genesys servers such as Configuration Server, Stat Server, SIP Server, and Interaction Server.
- Core Services: These services are used to store Web Service and Applications configuration and authentication.
- UI Services: These services provide user interfaces (Workspace Web and Application Splash page with login UI) and underlying service to drive the interfaces (Workspace Service and Data Collector).
- Client Application/Browser: This can be Workspace Web Edition Agent Desktop, a custom desktop or Gplus Adapter for Salesforce.
Reverse Proxy Service is used as an Ingress Controller. This works as an internal Application Load Balancer (ALB).
Data Services
GWS v9 uses multiple data sources to store its data. PostgreSQL
- GWS-specific configuration details (contact center & environment) are stored.
- Data stored in PostgreSQL is persistent.
Redis
- Redis is used for system-wide caching, where concurrent requests are served from Cache.
- Data stored in Redis is not persistent. It is always runtime.
Elastic Search
- Elastic Search searchable data from the Configuration Server which used by WWE and other services.
- Elastic Search used to store statistical information for WWE related functionality.
- Data stored in Elastic Search is not persistent. It is always runtime.
CometD
Web Services uses CometD version 3, an HTTP-based routing bus that uses an Ajax Push technology pattern known as Comet. Comet is a web application model that allows an HTTP request to push data to a browser, even if the browser has not requested it.
Web Services uses CometD to deliver unsolicited notifications to clients for real-time events, such as getting a new call or chat message. At runtime, CometD delivers messages, providing clients with a consistent approach while maintaining support for multiple browsers.
For details about CometD, see http://cometd.org/.