Deployment scenarios

Devo Endpoint Agent supports a range of different scenarios and boasts a flexible architecture. This document depicts the main deployment scenarios that can be considered.

Standalone deployment

Standalone deployment fully controlled by the Devo EA-Deployer with the standard use case:

Open

• Devo EA Manager running as a service in the host.

• 2 Dockers:

  • MySQL docker

  • REDIS docker

• Devo EA Manager and endpoints can both be located on the same network or can communicate via the Internet.

• The standalone deployment is the easiest way of deploying the Endpoint Agent solution but it is not a solution recommended for production environments as it does not include High Availability in any of the components.

• When automatically deploying dockers included in the Devo EA Deployer, keep in mind the following:

  • The dockers created by the EA deployer are exposed to the internal network. If you want to have a more restricted scenario you can restrict the access at your environment level.

  • REDIS database is created without a password by default. If you want to have a REDIS DB protected with a password, you should deploy your own REDIS server as the EA deployer does not create a password for REDIS.

Distributed deployments

There are several options when it comes to distributed deployment:

Open

• Devo EA 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 EA 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 EA 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. From EA 1.2.1, standard REDIS cluster is supported. 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).

• Recommended versions for REDIS and MySQL:
  MySQL, at least 5.7
  REDIS 5