BRIX On-Premises / Prepare BRIX On-Premises infrastructure

Prepare BRIX On-Premises infrastructure

An infrastructure is a set of components necessary for operation of the BRIX application. Depending on the objectives, the approaches and requirements for organizing an BRIX On-Premises infrastructure differ.

Let’s take a look at the following infrastructure organization options:

  • Infrastructure for familiarization.
  • Development/test environment infrastructures.
  • Production environment infrastructures.
  • High availability production environment infrastructures.

Начало внимание

You can choose one of the infrastructure organization options.

Конец внимание

Infrastructure for familiarization

This infrastructure organization option is suitable for familiarization purposes and does not require high reliability of storage components.

  1. Environment with Internet access and embedded databases.

infrastructure-preparation-1

Characteristics:

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

For more information on how to deploy this type of infrastructure, see Install BRIX Standard.

  1. Environment with Internet access and external databases.

infrastructure-preparation-2

Characteristics:

  • One physical server or virtual machine for BRIX On-Premises, proxying components, and data storage.
  • Two physical servers or two virtual machines for the external database.
  • Installation with Internet access.
  • Embedded storage components: RabbitMQ, Valkey or Redis, MongoDB.
  • External data storage components: PostgreSQL, MinIO (S3).

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

  1. Environment without Internet access with external databases.

infrastructure-preparation-8

Characteristics:

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

For more information on how to deploy this type of infrastructure, see Install BRIX Standard offline.

Development/test environment infrastructures

This infrastructure organization option is suitable for development and test environments and does not require the increased reliability of storage components.

  1. Environment with Internet access.

infrastructure-preparation-3

Characteristics:

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

For more information on how to deploy this type of infrastructure, read the following articles:

  1. Environment without Internet access.

infrastructure-preparation-4

Characteristics:

  • One physical server or virtual machine for BRIX On-Premises and data storage components.
  • One physical server or virtual machine for Kubernetes image storage.
  • Installation without Internet access.
  • Local Kubernetes image storage.
  • Embedded data storage components.

For more information on how to deploy this type of infrastructure for BRIX Standard, see:

  • For BRIX Standard KinD:

Production environment infrastructure

A variant of infrastructure organization for operational environments (Production).

  1. Environment with Internet access.

infrastructure-preparation-5

Characteristics:

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

For more information on how to deploy this type of infrastructure for BRIX Standard, see:

  1. Environment without Internet access.

infrastructure-preparation-6

Characteristics:

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

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

High availability production environment infrastructure

The infrastructure organization option is suitable for operational environments (production) with high reliability requirements for storage components.

infrastructure-preparation-07

Characteristics:

  • 10 physical servers or virtual machines for the Kubernetes cluster that will host BRIX On-Premises and data storage components.
  • 10 physical servers or virtual machines for external databases.
  • Two physical servers or virtual machines for balancing and proxying incoming requests to BRIX On-Premises and S3 storage.
  • One physical server or virtual machine for Kubernetes image storage.
  • Installation without Internet access.
  • Local Kubernetes image store.
  • Embedded high availability RabbitMQ and Valkey or Redis data storage components.
  • External high availability MongoDB, PostgreSQL, and S3 MinIO data storage components.
  • External high availability HAProxy proxy server for proxying incoming requests to BRIX On-Premises and S3 storage.

For more information on how to deploy this type of infrastructure for BRIX Enterprise, see: