Hardware recommendations for hosting Compose
There is no official minimum for the hardware requirements that are needed to host Compose Software. The recommended hardware specifications depend on different factors based on the services your Compose installation is running. You should taken into account
whether you’re expecting high-traffic or low-traffic,
the number of visitors per day/month,
maximum number of simultaneous visitors (during periods of high-traffic).
Requirements for Web and Database Servers
With higher traffic or density of high-traffic, the hardware specifications of the Web and database servers are higher too. The minimum Web server requirements are for a single installation of a low-traffic Compose installation with low-traffic, aka. a minor amount of visitors. To run multiple environments (test and production) and customized solutions you should use the recommended or higher hardware requirements.
Item | Web server (minimal) | usecompose CCM (recommended) | Combined Web & Database Server (minimal) | Combined Web & Database Server (recommended) |
Processor | 1 x CPU | 2 x CPU | 2 x CPU | 2 x CPU |
RAM | 4 GB RAM | 4 GB RAM | 4 GB RAM | 8 GB RAM |
HDD | 1 x 40 GB of free space or more is recommended for the webstore data (non-system drive is preferred) | |||
Recommended Microsoft Azure Virtual Machine Configuration | Standard B1ms (2 x CPU & 2 GB RAM) | Standard B2s (2 x CPU & 4 GB RAM) | Standard A2 (2 x CPU & 3,5 GB RAM) | Standard B2ms (2 x CPU & 8 GB RAM) |
Compose inbound Traffic with Azure Public Load Balancer
For inbound traffic, a public load balancer distributes traffic to the inbound firewalls. To simplify firewall configuration, the front-end public IP address is associated with a DNS name, and floating IP is enabled on the load-balancer rules. The load-balancer rules forward the required web service ports to the firewalls. Common ports required for inbound traffic include TCP/80 (HTTP) and TCP/443 (HTTPS).
The public load balancer’s health probes monitor firewall availability through the HTTPS or SSH services activated in the interface management profile. Only traffic sourced from the health probe IP address can connect to the HTTPS or SSH services.