Deployment scenarios

Devo Endpoint Agent supports a range of different scenarios and boasts a flexible architecture. This page outlines the main deployment scenarios.

If your use case does not apply to any of the following scenarios, contact Devo to explore different deployment options.

Standalone deployment

Standalone deployment fully controlled by the Endpoint Agent deployer with the standard use case:

Devo Endpoint Agent Manager running as a service in the host.
Two Dockers:
- MySQL docker
- REDIS docker
Devo Endpoint Agent 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:

Devo Endpoint Agent 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.

Devo Endpoint Agent deployer can deploy in a distributed fashion, it automatically deploys 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 Endpoint Agent 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 redirections. Furthermore, data acquisition and delivery toward Devo continues working in the event of a temporary REDIS outage, impacting only live queries (queries triggered from the web UI).

Recommended versions for REDIS and MySQL: