You can increase or decrease the number of running instances of your deployed services to meet demand.
The Northflank load-balancer will automatically ensure an even distribution of traffic to each running instance, avoiding containers that are initialising, terminating, or failing.
Each instance created will have the same resources (compute power, memory and storage) as configured in the service.
Scaling a database or addon will create additional replicas of the database or storage to increase availability, however this works differently depending on the type of database/addon.
You can increase or decrease the number of instances from the service overview using the scaling button in the header, or from the resources page.
Each instance will have the same resources as is configured for the service and Northflank will begin sending traffic to the new containers when they enter a healthy state.
Scaling a service to 0 instances will make it unavailable. If you leave CI enabled the service will still build the latest commit to the linked repository, if you leave CD enabled it will also deploy that latest build when scaled up again.
You can select the number of replica sets your database will use to increase availability, these replica sets contain a copy of the database to improve availability.
Databases can be scaled up from the resources page but cannot be scaled down. Any increase will be permanent.
See database scaling for more detailed information.
Scale a database
Increase the storage size, number of replicas, and the available CPU and memory to improve availability and performance.
Increase CPU and memory
Power-up your services by adding memory and moving from shared to dedicated CPU usage.
Increase the persistent storage available for your replicas.
Configure continuous integration and continuous delivery on your Northflank services.