OTH Public Software

Server Architecture

 Notice

This only applies to ansible based environments

Depending of the customers use-case, an OTH installation can take on different configurations. Below is an outline of the most commonly used setups. Network architecture

The load-balancer node should be the only node placed in a DMZ, with a public facing interface exposed to the Internet and a local LAN (rfc1918) interface, facing the application nodes and the database/storage node network. Application nodes and database nodes should be configured with local LAN (rfc1918) interfaces only.

Test/Demo or low volume production setup

Use-case

Typical use-case for test and demo setups are, testing clinical flows, trying out new releases, education, pilot trial runs, development or production setup with a low volume of patients/measurements.

Small scale setup

Node requirements

Node role Node count Additional info
Frontend 1 Mandatory
Application 1 Mandatory
Storage/DB 1 Optional
See requirements for further info

Normal scale production

Use-case

Typical use-case for normal scale production. Application servers could be setup as one large node, by scaling up on vCPU and Memory.

Normal scale setup

Node requirements

Node role Node count Additional info
Frontend 1 Mandatory
Application 2 Mandatory
Storage/DB 1 Optional
See requirements for further info

Large scale production

For larger scale production setups, add additional application nodes and if needed additional frontends.