Single host configuration

In a single host system, all System Platform components are installed on VMs hosted on a single hypervisor. Each VM can contain a different System Platform component, such as the IDE, Galaxy Repository, Historian Server, visualization nodes, and Application Object Servers. With a single host, you can build application redundancy. However, this configuration does not support hardware redundancy.

Important! Because a single host configuration does not provide any hardware redundancy, it is not recommended for a production environment. A single host means there is a single point of failure.

HIST1 and HIST2: Redundant Historian servers
VIS1: Visualization node
AOS1 and AOS2: Redundant Application Object servers
GR: Galaxy Repository and development node with IDE
VM Host: Virtualization layer

While a single VM can host multiple AVEVA System Platform components (for example, an "all-in-one node" installation), it is recommended that you distribute the components across two or more VMs. A single VM architecture is not ideal for production due to resource contention, as well as it being a source of multiple, single points of failure. While you can implement redundancy at the application level, there is no redundancy at the hardware level.

We recommend using standalone virtual machines where each component (for example, the Galaxy Repository, Application Object Server runtime nodes, and Historian) runs on its own dedicated VM. This kind of single server system can work for small to medium-sized systems with dedicated roles per VM.

A single host architecture provides certain advantages:

• It is the easiest to configure and size.

• It is the easiest to manage.

• It is less expensive to configure than other virtualized architectures, so it's good for small applications and limited budgets.

There are also several disadvantages:

• Since there is no hardware redundancy, a single host architecture leaves your system vulnerable to a single point of failure, including:

  • Hardware failures

  • Network disruptions

  • Power outages

• Correctly sizing the system can be difficult and more costly than anticipated, depending on the complexity of your System Platform configuration.

• It may be difficult to adequately scale the system as your configuration grows and your application expands.