Skip to content

feat(serverless): autoscaling concept #4312

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jan 31, 2025
Merged

feat(serverless): autoscaling concept #4312

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
fa86c26
feat(serverless): autoscaling concept
thomas-tacquet Jan 29, 2025
368bdb4
Apply suggestions from code review
thomas-tacquet Jan 29, 2025
85b93c2
missed review
thomas-tacquet Jan 29, 2025
17aceff
Apply suggestions from code review
thomas-tacquet Jan 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions pages/serverless-containers/concepts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,16 @@ categories:
- serverless
---

## Autoscaling

Autoscaling refers to the ability of Serverless Containers to automatically adjust the number of instances without manual intervention.
Scaling mechanisms ensure that resources are provisioned dynamically to handle incoming requests efficiently while minimizing idle capacity and cost.

Autoscaling parameters are [min-scale](/serverless-containers/concepts/#min-scale) and [max-scale](/serverless-containers/concepts/#max-scale). Available scaling policies are:
* **Concurrent requests:** requests incoming to the resource at the same time. Default value suitable for most use cases.
* **CPU usage:** to scale based on CPU percentage, suitable for intensive CPU workloads.
* **RAM usage** to scale based on RAM percentage, suitable for memory intensive workloads.

## Cold start

Cold start is the time a Container takes to handle a request when it is called for the first time.
Expand Down Expand Up @@ -182,10 +192,6 @@ A sandbox is an isolation area for your container. Serverless Containers offer t

One of the advantages of Serverless Containers is that when your container is not triggered, it does not consume any resources, which enables great savings.

## Scaling

Serverless Containers make scaling your application transparent, up to 50 instances of your container can be run at the same time.

## Secrets

Secrets are an extra-secure type of environment variable. They are environment variables that are injected into your container and stored securely, but not displayed in the console after initial validation.
Expand Down
14 changes: 10 additions & 4 deletions pages/serverless-functions/concepts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,16 @@ categories:
- serverless
---

## Autoscaling

Autoscaling refers to the ability of Serverless Functions to automatically adjust the number of instances without manual intervention.
Scaling mechanisms ensure that resources are provisioned dynamically to handle incoming requests efficiently while minimizing idle capacity and cost.

Autoscaling parameters are [min-scale](/serverless-functions/concepts/#min-scale) and [max-scale](/serverless-functions/concepts/#max-scale). Available scaling policies are:
* **Concurrent requests:** requests incoming to the resource at the same time. Default value suitable for most use cases.
* **CPU usage:** to scale based on CPU percentage, suitable for intensive CPU workloads.
* **RAM usage** to scale based on RAM percentage, suitable for memory intensive workloads.

## Build step

Before deploying Serverless Functions, they have to be built. This step occurs during deployment.
Expand Down Expand Up @@ -142,10 +152,6 @@ A sandbox is an isolation area for your function. Serverless Functions offer two

One of the advantages of Serverless Functions is that when your function is not triggered, it does not consume any resources, which allows for significant savings.

## Scaling

Serverless Functions make scaling your application transparent, up to 50 instances of your function can be run at the same time.

## Secrets

Secrets are an extra-secure type of environment variable. They are environment variables that are injected into your function and stored securely, but not displayed in the console after initial validation.
Expand Down