BRIX On-Premises / BRIX On-Premises Standard

BRIX On-Premises Standard

BRIX On-Premises Standard installation options:

Infrastructure for familiarization

The BRIX Standard installation option is suitable for familiarization purposes and does not require high reliability of data storage components.

elma365-on-premises-standard-1

Characteristics:

  • One physical server or virtual machine.
  • Installation with Internet access.
  • Embedded data storage components.

Installation is described in Install BRIX Standard trial version.

Development/test environment infrastructure

This infrastructure option is suitable for development (DEV) and testing (TEST) environments and does not require high reliability of data storage components.

elma365-on-premises-standard-3

Characteristics:

  • One physical server or virtual machine for all components.
  • Installation with Internet access.
  • Embedded data storage components.

For more information on how to deploy this infrastructure option for BRIX Standard KinD, see the Install BRIX Standard in KinD article.

Production environment infrastructure

  1. Option for deploying infrastructure for production environments (PROD) in KinD.

elma365-on-premises-standard-2

Characteristics:

  • One physical server or virtual machine for BRIX On‑Premises, proxying, and data storage components.
  • Two physical servers or virtual machines for external databases.
  • Installation with Internet access.
  • Embedded RabbitMQ, Redis, and MongoDB data storage components.
  • External PostgreSQL and MinIO S3 data storage components.

To install, read the following articles:

  1. PostgreSQL.
  2. MinIO S3
  3. Install BRIX Standard in KinD.
  1. Option for deploying infrastructure for production environments (PROD) in Kubernetes.

elma365-on-premises-standard-4

Characteristics:

  • One physical server or virtual machine for BRIX On‑Premises, proxying, and data storage components.
  • Three physical servers or virtual machines for external databases.
  • Installation with Internet access.
  • Embedded RabbitMQ, Valkey, or Redis data storage components.
  • External PostgreSQL and MinIO S3 data storage components.
  • Embedded HAProxy proxy server for proxying incoming requests to external S3 storage.

For more information on how to deploy this infrastructure option for BRIX Standard Kubernetes, see the following articles: