scaleway · SamyOubouaziz · Jan 29, 2025 · Jan 21, 2025 · Jan 21, 2025 · Jan 21, 2025
@@ -142,6 +142,13 @@ Only one HTTP port can be exposed per Serverless Container.
 
 A container's privacy policy defines whether a container may be invoked anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-containers/#authentication) (**private**).
 
+## Queue trigger
+
+A queue trigger is a mechanism that connects a container to a queue created with [Scaleway Queues](/serverless/messaging/concepts/#queues), and invokes the container automatically whenever a message is added to the queue.
+
+For each message that is sent to a queue, the trigger reads the message and invokes the associated container with the message as the input parameter.
+The container can then process the message and perform any required actions, such as updating a database or sending a notification.
+
 ## Registry endpoint
 
 The registry endpoint parameter is the resource linked to the container image used in your Serverless Container.
@@ -154,6 +161,17 @@ Use cases:
 * **Shorter timeouts:** Ideal for use cases with quick, predictable response times, such as HTTP APIs or real-time applications.
 * **Longer timeouts:** Useful for tasks requiring extended processing times, like data processing, report generation, or integration with slower external services.
 
+## Rolling update
+
+When deploying a new version of a Serverless Container, a rolling update is applied by default. This means that the new version of the service is gradually rolled out to your users without downtime.
+Here is how it works:
+
+* When a new version of your container is deployed, the platform automatically starts routing traffic to it incrementally, while still serving requests from the old version until the new one is fully deployed.
+* Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime.
+* The old version is decommissioned once the new version is fully serving traffic.
+
+This process ensures a seamless update experience, minimizing user disruption during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to it.
+
 ## Sandbox
 
 A sandbox is an isolation area for your container. Serverless Containers offer two sandboxing environments:
@@ -180,33 +198,21 @@ Serverless allows you to deploy your Functions (FaaS) and Containerized Applicat
 
 Serverless.com (Serverless Framework) is a tool that allows you to deploy serverless applications without having to manage Serverless Container's API call. Write and deploy a YAML configuration file, everything else is handled automatically, even the image building.
 
-## Serverless Function
+## Serverless Containers
 
-Serverless Functions are serverless, fully managed compute services that allow you to run small, stateless code snippets or functions in response to HTTP requests or events.
+Serverless Containers is a fully managed service that enables you to run containerized applications in a scalable and serverless environment.
 
-These functions automatically scale based on demand and are designed to be lightweight, event-driven, and easily deployable, eliminating the need to worry about infrastructure management. Functions is built on top of Serverless Containers, meaning you can run your functions packaged in containers and have them scale efficiently.
-
-## Serverless Job
+It automatically handles infrastructure management, scaling, and load balancing, allowing you to focus on writing code without worrying about servers or clusters. Serverless Containers supports any language, framework, or binary that can run in a container, and it integrates seamlessly with other Scaleway services, making it ideal for deploying modern, event-driven, and API-based applications.
 
-Serverless Jobs are similar to Serverless Containers but are better suited for running longer workloads. See [the comparaison between Serverless products](/serverless-containers/reference-content/difference-jobs-functions-containers) for more information.
-
-## Queue trigger
-
-A queue trigger is a mechanism that connects a container to a queue created with [Scaleway Queues](/messaging/concepts/#queues), and invokes the container automatically whenever a message is added to the queue.
-
-For each message that is sent to a queue, the trigger reads the message and invokes the associated container with the message as the input parameter.
-The container can then process the message and perform any required actions, such as updating a database or sending a notification.
+## Serverless Functions
 
-## Rolling update
+Serverless Functions are fully managed compute services that allow you to run small, stateless code snippets or functions in response to HTTP requests or events.
 
-When deploying a new version of a Serverless Container, a rolling update is applied by default. This means that the new version of the service is gradually rolled out to your users without downtime.
-Here is how it works:
+These functions automatically scale based on demand and are designed to be lightweight, event-driven, and easily deployable, eliminating the need to worry about infrastructure management. Functions is built on top of Serverless Containers, meaning you can run your functions packaged in containers and have them scale efficiently.
 
-* When a new version of your container is deployed, the platform automatically starts routing traffic to the new version incrementally, while still serving requests from the old version until the new one is fully deployed.
-* Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime.
-* The old version is decommissioned once the new version is fully serving traffic.
+## Serverless Jobs
 
-This process ensures a seamless update experience, minimizing user disruption during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to it
+Serverless Jobs are similar to Serverless Containers but are better suited for running longer workloads. See [the comparison between Serverless products](/serverless-containers/reference-content/difference-jobs-functions-containers) for more information.
 
 ## Stateless
 

@@ -158,15 +158,21 @@ Serverless allows you to deploy your Functions (FaaS) and Containerized Applicat
 
 Serverless.com (Serverless Framework) is a tool that enables the deployment of serverless applications without having to manage Serverless Function's API call. Just write your configuration in a YAML and deploy, it handles everything.
 
-## Serverless Function
+## Serverless Containers
 
-Serverless Functions are serverless, fully managed compute services that allow you to run small, stateless code snippets or functions in response to HTTP requests or events.
+Serverless Containers is a fully managed service that enables you to run containerized applications in a scalable and serverless environment.
+
+It automatically handles infrastructure management, scaling, and load balancing, allowing you to focus on writing code without worrying about servers or clusters. Serverless Containers supports any language, framework, or binary that can run in a container, and it integrates seamlessly with other Scaleway services, making it ideal for deploying modern, event-driven, and API-based applications.
+
+## Serverless Functions
+
+Serverless Functions are fully managed compute services that allow you to run small, stateless code snippets or functions in response to HTTP requests or events.
 
 These functions automatically scale based on demand and are designed to be lightweight, event-driven, and easily deployable, eliminating the need to worry about infrastructure management. Functions is built on top of Serverless Containers, meaning you can run your functions packaged in containers and have them scale efficiently.
 
-## Serverless Job
+## Serverless Jobs
 
-Serverless Jobs are similar to Serverless Functions but are better suited for running longer workloads. See [the comparaison between Serverless products](/serverless-functions/reference-content/difference-jobs-functions-containers) for more information.
+Serverless Jobs are similar to Serverless Containers but are better suited for running longer workloads. See [the comparison between Serverless products](/serverless-functions/reference-content/difference-jobs-functions-containers) for more information.
 
 ## Stateless
 

@@ -60,6 +60,22 @@ Performance metrics for your Serverless resources are natively available: see [m
 
 A schedule (cron) is a mechanism used to automatically start a Serverless Job at a specific time on a recurring schedule. It works similarly to a traditional Linux cron job, using the `* * * * *` format. Refer to our [cron schedules reference](/serverless-jobs/reference-content/cron-schedules/) for more information.
 
+## Serverless Containers
+
+Serverless Containers is a fully managed service that enables you to run containerized applications in a scalable and serverless environment.
+
+It automatically handles infrastructure management, scaling, and load balancing, allowing you to focus on writing code without worrying about servers or clusters. Serverless Containers supports any language, framework, or binary that can run in a container, and it integrates seamlessly with other Scaleway services, making it ideal for deploying modern, event-driven, and API-based applications.
+
+## Serverless Functions
+
+Serverless Functions are fully managed compute services that allow you to run small, stateless code snippets or functions in response to HTTP requests or events.
+
+These functions automatically scale based on demand and are designed to be lightweight, event-driven, and easily deployable, eliminating the need to worry about infrastructure management. Functions is built on top of Serverless Containers, meaning you can run your functions packaged in containers and have them scale efficiently.
+
+## Serverless Jobs
+
+Serverless Jobs are similar to Serverless Containers but are better suited for running longer workloads. See [the comparison between Serverless products](/serverless-jobs/reference-content/difference-jobs-functions-containers) for more information.
+
 ## Secrets reference
 
 A secret reference is a mechanism that allows you to use a secret stored in [Secret Manager](/secret-manager/) within Serverless Jobs. It allows you to securely reference sensitive data, such as API secret keys, passwords, tokens, or certificates.