Skip to main content

Concepts

In accordance with the SHIPOPS principle, users are not required to know infrastructure technologies. SHIPOPS supports the main business cases while helping save server resources and, therefore, the user's budget. At the same time, SHIPOPS offers a compromise between savings and reliability.

Core Infrastructure Entities

A Server performs separate infrastructure functions in the project: Roles, such as cluster component, builder, registry, DNS server, and VPN server. Multiple roles can be placed on one server to save resources.

Kubes are used as components that run the project's business logic, and a Cluster is used for scaling and high service availability.

Network Model

All infrastructure elements are combined in the "virtual private cloud" (VPC) component, which ensures secure interaction between them.