Devo Universal Agent supports a range of different of scenarios and boasts a flexible architecture. This documents depicts the main deployment scenarios that can be considered.
If your use case does not apply to any of the following scenarios, please contact Devo to explore different deployment options.
Standalone deployment fully controlled by the Devo UA-Deployer with the standard use case:
- Devo UAM running as a service in the host.
- 2 Dockers:
- MySQL docker
- REDIS docker
- Devo UA Manager and endpoints can both be located on the same network or can communicate via the Internet.
There are several options when it comes to distributed deployment:
High Availability UA Manager
- Devo UA Deployer can automatically deploy several replicas of the manager.
- A Load Balancer needs to be deployed separately and configured with HTTPS listeners. Same certificates need to be configured on it to face the endpoints.
REDIS and MySQL
- Devo UA Deployer can deploy in a distributed fashion, it will automatically deploy a dockerized version of MySQL and REDIS on the server at the moment of installation.
- If the deployment scenario requires clustering for REDIS and MySQL, Devo UA Deployer cannot provide the automatic deployment but it is possible to use existing clusters. This kind of basic cluster deployment can be provided separately.
- REDIS clusterization (*) is supported in Active-Passive mode—that is to say that only one node is available at a time, since the underlying library that handles connections does not support re-directions. Furthermore, data acquisition and delivery toward Devo would continue working in the event of a temporary REDIS outage, impacting only Live Queries (queries triggered from the WEB UI).