Golang Hosting

The platform provides managed Go environments for projects of different sizes and purposes. This guide covers environment creation, supported Golang versions, Git-based deployment, custom domains, and automatic vertical and horizontal scaling.

Go Environment Hosting

Create the required environment through the topology wizard. Open the Go engine tab, add Golang as the application server, and include any additional stacks required by the project, such as load balancers, databases, or shared storage.

• Set the required application-server node count.
• Configure the RAM and CPU Cloudlet limits.
• Attach public IP addresses when direct external access is required.
• Add supporting database, load-balancing, or storage nodes.

Golang Versioning

The currently documented Golang stack versions are:

Select the required version during environment creation. It can be changed later through container redeployment while preserving custom data inside the affected node or layer.

Go Application Deployment

After environment creation, deploy the Go project from a Git repository. Deployment from an application archive is described by the source documentation as a planned capability for a future platform release.

The deployment process can be customized with the following container variables:

During deployment, the platform automatically:

• Parses the Git URL to obtain the Go project location.
• Downloads the project and dependencies with go get.
• If dependency retrieval fails, downloads it as a regular Git project and retries.
• Builds the project with go build and the options supplied through GO_BUILD_OPTIONS.
• Runs the binary selected through GO_RUN, applying any GO_RUN_OPTIONS.
• Stores the deployed project under the directory defined by GOPATH.

Domains Management

Bind a custom domain to the Go application instead of using the default environment address.

Automatic Vertical Scaling

Set the lower and upper Cloudlet limits for the Go server in the topology wizard. The platform dynamically changes the available RAM and CPU within these limits according to current demand.

One Cloudlet equals 128 MiB of RAM and 400 MHz of CPU.

The application consumes fewer resources when load is low and can scale up to the configured limit as demand increases. Resource charging is based on actual consumption.

Manual Horizontal Scaling

Add extra Golang servers through the topology wizard during environment creation or later adjustment. Use the plus control in the Horizontal Scaling section to choose the required number of instances.

• The same-type node limit depends on the hosting provider.
• The commonly documented limit is 16 nodes and can be increased through a support request.
• A load-balancing node is added automatically when the Golang application-server layer is scaled.

Automatic Horizontal Scaling

Open Settings > Monitoring > Auto Horizontal Scaling and add triggers that increase or decrease the number of Golang nodes according to application load.

• Select the required stack or layer.
• Choose the monitored resource: CPU, RAM, Network, or Disk.
• Set the scaling threshold and monitoring conditions.
• Define the node adjustment and permitted node-count range.

Additional Platform Features

• Custom SSL and Built-In SSL
• Public IPv4 and IPv6 addresses
• A broad selection of managed databases
• Container firewalls, endpoints, and environment isolation
• Dashboard management and direct SSH access
• Open API and Cloud Scripting automation
• Pay-as-you-use pricing
• Collaboration features for teams
• Multi-cloud distribution

Expected Result

A managed Golang environment is created with the selected Go version, resource limits, networking, and supporting services. The project can be deployed from Git, connected to a custom domain, and scaled vertically or horizontally according to application demand.

Important Notes

• Use the Software Stack Versions document to confirm the current Go releases.
• The source guide documents Git repository deployment rather than archive deployment.
• Review GO_RUN, GOPATH, GO_BUILD_OPTIONS, and GO_RUN_OPTIONS before deployment.
• A load balancer is added automatically when the Go layer is horizontally scaled.
• A public IP is suitable for production traffic and direct DNS A-record access.
• Check provider-specific node limits before large-scale expansion.