Create a Java service in Zerops
Zerops provides a Java runtime service with extensive build support. Java runtime is highly scalable and customisable to suit both development and production.
Create Java service using Zerops GUIβ
First, set up a project in Zerops GUI. Then go to the project dashboard page and choose Add new service in the left menu in the Services block. Then add a new Java service:
// TODO screenshot (add a new service page)
Choose Java versionβ
Following Java major versions are currently supported:
- 17
- 21
You can change the major version at any time later.
Set a hostnameβ
Enter a unique service identifier like "app","cache", "gui" etc. Duplicate services with the same name in the same project are forbidden.
Limitations:β
- maximum 25 characters
- must contain only lowercase ASCII letters (a-z) or numbers (0-9)
The hostname is fixed after the service is created. It can't be changed later.
Set secret environment variablesβ
Add environment variables with sensitive data, such as password, tokens, salts, certificates etc. These will be securely saved inside Zerops and added to your runtime service upon start.
Setting the secret environment variables is optional. You can set them later in Zerops GUI.
Read more about different types of env variables in Zerops.
Set auto scaling configurationβ
Zerops scales the Java services automatically both vertically and horizontally. Vertical scaling means increasing or decreasing the hardware resources (CPU, RAM and disk) of a Java container. Horizontal scaling adds or removes whole containers.
CPU Modeβ
Shared Your application gets a full physical CPU core, but it is shared with up to 10 other applications. In this mode the power your application gets is depended on other applications running on the same CPU core. At best case scenario your application gets 10/10 of CPU core power and 1/10 at worst case scenario.
Dedicated The CPU core is dedicated to your application.
See the pricing for the difference between CPU modes.
Choose the CPU mode when starting a new service or change it later. The CPU mode doesn't change automatically.
Vertical auto scalingβ
Vertical auto scaling has following default configuration:
Resources Type | Minimum resource | Maximum resource |
---|---|---|
CPU cores | 1 | 5 |
RAM | 0.25 GB | 32 GB |
Disk | 1 GB | 100 GB |
Java service always starts with the minimal resources.
For most cases, the default parameters will work without issues. If you need to limit the cost of the Java service, lower the maximal resources. Zerops will never scale above the selected maximums.
When you are experiencing problems with insufficient Java performance or capacity, increase the minimal resources. Zerops will never scale below the selected minimums.
Learn more about how to fine tune the auto scaling to fit your application needs.
You can change the vertical auto scaling parameters later.
Horizontal auto scalingβ
When a container needs more CPU or RAM but already consumes maximal resources defined for the vertical auto scaling, Zerops will add a new container to your Java service. When your Java service doesn't need so much power and all containers are vertically scaled down in such a way their CPU allocation is near the minimal resources, Zerops will gradually remove whole containers.
Horizontal auto scaling has following default configuration:
minimum containers | 1 |
maximum containers | 6 |
Java service always starts with the minimum number of containers.
You can increase the minimum or decrease the maximum number of containers. The horizontal scaling parameters can be changed later.
Learn more about Java auto scaling.
Single container vs. High Availabilityβ
When creating a new runtime service, you can choose the minimum and maximum number of containers. If you set the maximum limit to one, the service will be run in a single container and no horizontal scaling will occur.
If the single container fails, Zerops will start a new container and deploy your application automatically. The application won't be available for a short period. This mode is recommended for non-critical applications or dev environments.
By increasing the maximum number of containers for your service, you enable horizontal auto scaling. Zerops will then add containers depending on your applicationβs load. Application running on two or more containers is in High Availability mode, which we highly recommend for production. When the load drops, containers will be gradually removed to the defined minimum.
Each container of the same service is strictly installed on a different server. This prevents the temporary outage in case any of Zerops servers fail. If the connection to a container is broken, Zerops immediately redirects incoming traffic to other containers. A new container will be started automatically and the broken container will be deleted.
Check if your application is ready to be run in multiple containers.
Create Java service using zCLIβ
zCLI is the Zerops command-line tool. To create a new Java service via the command-line, follow these steps:
- Install & setup zCLI
- Create a project description file
- Create a project with a Java and PostgreSQL service
Create a project description fileβ
Zerops uses a yaml format to describe the project infrastructure.
Basic example:β
Create a directory my-project
. Create an description.yml
file inside the my-project
directory with following content:
# basic project data
project:
# project name
name: my-project
# array of project services
services:
- # service name
hostname: app
# service type and version number in java@{version} format
type: java@latest
# defines the minimum number of containers for horizontal autoscaling
minContainers: 1
# defines the maximum number of containers for horizontal autoscaling. Max value = 6.
maxContainers: 6
# optional: create env variables
envSecrets:
S3_ACCESS_KEY_ID: 'P8cX1vVVb'
S3_ACCESS_SECRET: 'ogFthuiLYki8XoL73opSCQ'
The yaml file describes your future project infrastructure. The project will contain one Java version 1 service with default auto scaling configuration. Hostname will be set to "app", the internal port(s) the service listens on will be defined later in the zerops.yml. Following secret env variables will be configured:
Full example:β
Create a directory my-project. Create an description.yml file inside the my-project directory with following content:
# basic project data
project:
# project name
name: my-project
# optional: project description
description: A project with a Java and PostgreSQL database
# optional: project tags
tags:
- DEMO
- ZEROPS
# array of project services
services:
- # service name
hostname: app
# service type and version number in java@{version} format
type: java@latest
# optional: vertical auto scaling customization
verticalAutoscaling:
cpuMode: DEDICATED
minCpu: 2
maxCpu: 5
minRam: 2
maxRam: 24
minDisk: 6
maxDisk: 50
startCpuCoreCount: 3
minFreeRamGB: 0.5
minFreeRamPercent: 20
# defines the minimum number of containers for horizontal autoscaling. Max value = 6.
minContainers: 2
# defines the maximum number of containers for horizontal autoscaling. Max value = 6.
maxContainers: 4
# optional: create secret env variables
envSecrets:
S3_ACCESS_KEY_ID: 'P8cX1vVVb'
S3_ACCESS_SECRET: 'ogFthuiLYki8XoL73opSCQ'
- # second service hostname
hostname: db
# service type and version number in postgresql@{version} format
type: postgresql@12
# mode of operation "HA"/"non_HA"
mode: NON_HA
The yaml file describes your future project infrastructure. The project will contain a Java service and a PostgreSQL service.
Java service with "app" hostname, the internal port(s) the service listens on will be defined later in the zerops.yml. Java service will run on version 1 with a custom vertical and horizontal scaling. Following secret env variables will be configured:
The hostname of the PostgreSQL service will be set to "db". The single container mode will be chosen and the default auto scaling configuration will be set.
Description of description.yml parametersβ
The project:
section is required. Only one project can be defined.
Parameter | Description |
---|---|
hostname | The unique service identifier. The hostname of the new database will be set to the
|
type | Specifies the service type and version. See what Java service types are currently supported. |
verticalAutoscaling | Optional. Defines custom vertical auto scaling parameters. All verticalAutoscaling attributes are optional. Not specified attributes will be set to their default values. |
- cpuMode | Optional. Accepts |
- minCpu/maxCpu | Optional. Set the minCpu or maxCpu in CPU cores (integer). |
- minRam/maxRam | Optional. Set the minRam or maxRam in GB (float). |
- minDisk/maxDisk | Optional. Set the minDisk or maxDisk in GB (float). |
minContainers | Optional. Default = 1. Defines the minimum number of containers for horizontal autoscaling. Limitations:Current maximum value = 6. |
maxContainers | Defines the maximum number of containers for horizontal autoscaling. Limitations:Current maximum value = 6. |
envSecrets | Optional. Defines one or more secret env variables as a key value map. See env variable restrictions. |
Create a project based on the description.ymlβ
When you have your description.yml
ready, use the zcli project project-import
command to create a new project and the service infrastructure.
Usage:
zcli project project-import importYamlPath [flags]
Flags:
-h, --help the project import command.
--orgId string If you have access to more than one organization, you must specify the org ID for which the
project is to be created.
--workingDie string Sets a custom working directory. Default working directory is the current directory. (default "./")
Zerops will create a project and one or more services based on the description.yml
content.
Maximum size of the description.yml
file is 100 kB.
You don't specify the project name in the zcli project project-import
command, because the project name is defined in the description.yml
.
If you have access to more than one client, you must specify the client ID for which the project is to be created. The clientID
is located in the Zerops GUI under the client name on the project dashboard page.
Add Java service to an existing projectβ
Example:β
Create a directory my-project
if it doesn't exist. Create an import.yml
file inside the my-project
directory with following content:
# basic project data
project:
# project name
name: my-project
# array of project services
services:
- # service name
hostname: app
# service type and version number in java@{version} format
type: java@latest
# defines the minimum number of containers for horizontal autoscaling
minContainers: 1
# defines the maximum number of containers for horizontal autoscaling. Max value = 6.
maxContainers: 6
# optional: create env variables
envSecrets:
S3_ACCESS_KEY_ID: 'P8cX1vVVb'
S3_ACCESS_SECRET: 'ogFthuiLYki8XoL73opSCQ'
The yaml file describes the list of one or more services that you want to add to your existing project. In the example above, one Java service version 1 with default auto scaling configuration will be added to your project. Hostname of the new service will be set to app
. Following secret env variables will be configured:
The content of the services:
section of import.yml
is identical to the project description file. The import.yml
never contains the project:
section because the project already exists.
When you have your import.yml
ready, use the zcli project service-import
command to add one or more services to your existing Zerops project.
zCLI commands are interactive, when you press enter after zcli project service-import importYamlPath
, you will be given a list of your projects to choose from.
Maximum size of the import.yml file is 100 kB.