feat(serverless): autoscaling concept (scaleway#4312)

* feat(serverless): autoscaling concept

* Apply suggestions from code review

Co-authored-by: Jessica <[email protected]>

* missed review

* Apply suggestions from code review

Co-authored-by: Rowena Jones <[email protected]>

---------

Co-authored-by: Jessica <[email protected]>
Co-authored-by: Rowena Jones <[email protected]>

Author: 3 people

pages/serverless-containers/concepts.mdx

@@ -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.
@@ -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.

pages/serverless-functions/concepts.mdx

@@ -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.
@@ -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.