| Line 14: | Line 14: | ||
Reverse Proxy Service is used as an Ingress Controller. This works as an internal Application Load Balancer (ALB). | Reverse Proxy Service is used as an Ingress Controller. This works as an internal Application Load Balancer (ALB). | ||
| − | == CometD== | + | ==Data Services== |
| + | '''PostgreSQL''' | ||
| + | * PostgreSQL is a simple and lightweight database. | ||
| + | * The configuration details are stored in PostgreSQL contact center and environment. | ||
| + | * PostgreSQL gets synced with the configuration server, seamlessly. | ||
| + | * Diverse indexing techniques and flexible full-text search are some of the key features of PostgreSQL, while it also supports Atomicity, Consistency, Isolation, Durability(ACID). | ||
| + | |||
| + | '''Redis''' | ||
| + | * Redis is used for system-wide caching, where concurrent requests are served from the cache. | ||
| + | * Redis is always in run-time mode. It is not persistent. | ||
| + | * TTL can be defined in Redis as per customer requirement. | ||
| + | |||
| + | '''Elastic Search''' | ||
| + | * This is a persistent storage. | ||
| + | * Elastic Search stores all the searchable data that can be searched from different services of Web Services. | ||
| + | * It contains most information from the configuration server. | ||
| + | * It is also used to store statistical information. | ||
| + | * Kibana can be used to view the Elastic Search data. | ||
| + | |||
| + | ==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 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. | ||
Revision as of 09:26, March 23, 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
PostgreSQL
- PostgreSQL is a simple and lightweight database.
- The configuration details are stored in PostgreSQL contact center and environment.
- PostgreSQL gets synced with the configuration server, seamlessly.
- Diverse indexing techniques and flexible full-text search are some of the key features of PostgreSQL, while it also supports Atomicity, Consistency, Isolation, Durability(ACID).
Redis
- Redis is used for system-wide caching, where concurrent requests are served from the cache.
- Redis is always in run-time mode. It is not persistent.
- TTL can be defined in Redis as per customer requirement.
Elastic Search
- This is a persistent storage.
- Elastic Search stores all the searchable data that can be searched from different services of Web Services.
- It contains most information from the configuration server.
- It is also used to store statistical information.
- Kibana can be used to view the Elastic Search data.
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/.