feat(serverless): update concepts (#4150)

* feat(serverless): update concepts

* update faq

* rolling update

* more faq entries

* opti blocked ports

* Apply suggestions from code review

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

* Apply suggestions from code review

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

* Apply suggestions from code review

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

* Apply suggestions from code review

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

* apply comments

* Update faq/serverless-jobs.mdx

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

---------

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

Author: 3 people

faq/serverless-containers.mdx

@@ -10,6 +10,49 @@ category: serverless
 productIcon: ContainersProductIcon
 ---
 
+## What is serverless computing, and how does it differ from traditional cloud hosting?
+
+Serverless computing is a cloud execution model where the cloud provider dynamically manages the allocation of compute resources. Unlike traditional hosting models, you do not need to provision, scale, or maintain servers. Instead, you focus solely on writing and deploying your code, and the infrastructure scales automatically to meet demand.
+
+## Why consider using Serverless Containers, Functions, or Jobs for my projects?
+
+These services allow you to build highly scalable, event-driven, and pay-as-you-go solutions. Serverless Containers and Functions help you create applications and microservices without worrying about server management, while Serverless Jobs lets you run large-scale, parallel batch-processing tasks efficiently. This can lead to faster development cycles, reduced operational overhead, and cost savings.
+
+## Can I run any application on Serverless Containers?
+
+Yes. Because Serverless Containers supports any containerized application, you can choose the language, runtime, and framework that best suits your needs. As long as it can run in a container and respond to HTTP requests, Serverless Containers can host it.
+
+## What are the cost benefits of using serverless services like Serverless Containers?
+
+With serverless, you only pay for the computing resources you use. There are no upfront provisioning costs or paying for idle capacity. When your application traffic is low, the cost scales down, and when traffic spikes, the platform automatically scales up, ensuring you never overpay for unused resources.
+
+## Can updates of Serverless Containers cause downtime?
+
+No, deploying a new version of your Serverless Container generates a **rolling update**. This means that a 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 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.
+
+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.
+
+## Can I upgrade Serverless Container resources (vCPU and RAM) at any time?
+
+Yes, Serverless Containers resources can be changed at any time without causing downtime - see the previous question for full details.
+
+## How does scaling work in these serverless services?
+
+Scaling in Serverless Containers and Serverless Functions is handled automatically by the platform. When demand increases - more requests or events - the platform spins up additional instances to handle the load. When demand decreases, instances spin down. This ensures optimal performance without manual intervention.
+
+## How do I integrate my serverless solutions with other Scaleway services?
+
+Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/serverless/messaging/concepts/#queues) and [Topics and Events](/serverless/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless/sql-databases/). [Serverless Jobs](/serverless/jobs/) can pull data from [Object Storage](/storage/object), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
+
+## Can I migrate existing applications to Serverless Containers?
+
+Yes. Many traditional applications can be containerized and deployed to Serverless Containers. This makes it easier to modernize legacy systems without a complete rewrite. By moving to a serverless platform, you gain automatic scaling, reduced operational overhead, and a simpler infrastructure management experience.
+
 ## Are applications deployed on Serverless Containers stateless?
 
 Yes, all applications deployed on Serverless Containers are stateless. This means the server does not store any state about the client session. Instead, the session data is stored on the client and passed to the server as needed.
@@ -143,4 +186,28 @@ solutions like Scaleway Object Storage.
 ## Why does my container have an instance running after deployment, even with min-scale 0?
 
 Currently, a new container instance will always start after each deployment, even if there is no traffic and the minimum
-scale is set to 0. This behavior is not configurable at this time.
+scale is set to 0. This behavior is not configurable at this time.
+
+## How can I store data in my Serverless resource?
+
+Serverless resources are by default [stateless](/serverless/containers/concepts/#stateless), local storage is ephemeral.
+
+For some use cases, such as saving analysis results, exporting data etc., it can be important to save data. Serverless resources can be connected to other resources from the Scaleway ecosystem for this purpose:
+
+### Databases
+
+* [Serverless Databases](/serverless/sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations.
+* [Managed MySQL / PostgreSQL](/managed-databases/postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
+* [Managed Database for Redis®](/managed-databases/redis/): Fully managed Redis®* in seconds.
+* [Managed MongoDB®](/managed-databases/mongodb/): Get the best of MongoDB® and Scaleway in one database.
+
+### Storage
+
+* [Object Storage](/storage/object/): Multi-AZ resilient object storage service ensuring high availability for your data.
+* [Scaleway Glacier](/storage/object/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
+
+<Message type="tip">
+Explore all Scaleway products in the console and select the right product for your use case.
+
+Further integrations are also possible even if not listed above, for example, [Secret Manager](/identity-and-access-management/secret-manager/) can help you to store information that requires versioning.
+</Message>

faq/serverless-functions.mdx

@@ -10,6 +10,41 @@ category: serverless
 productIcon: FunctionsProductIcon
 ---
 
+## What is serverless computing, and how does it differ from traditional cloud hosting?
+
+Serverless computing is a cloud execution model where the cloud provider dynamically manages the allocation of compute resources. Unlike traditional hosting models, you do not need to provision, scale, or maintain servers. Instead, you focus solely on writing and deploying your code, and the infrastructure scales automatically to meet demand.
+
+## Why consider using Serverless Containers, Functions, or Jobs for my projects?
+
+These services allow you to build highly scalable, event-driven, and pay-as-you-go solutions. Serverless Containers and Functions help you create applications and microservices without worrying about server management, while Serverless Jobs lets you run large-scale, parallel batch-processing tasks efficiently. This can lead to faster development cycles, reduced operational overhead, and cost savings.
+
+## What are the cost benefits of using serverless services like Serverless Containers and Serverless Functions?
+
+With serverless, you only pay for the computing resources you use. There are no upfront provisioning costs or paying for idle capacity. When your application traffic is low, the cost scales down, and when traffic spikes, the platform automatically scales up, ensuring you never overpay for unused resources.
+
+## How does scaling work in these serverless services?
+
+Scaling in Serverless Containers and Serverless Functions is handled automatically by the platform. When demand increases - more requests or events - the platform spins up additional instances to handle the load. When demand decreases, instances spin down. This ensures optimal performance without manual intervention.
+
+## Can updates of Serverless Function cause downtime?
+
+No, deploying a new version of your Serverless Function generates a **rolling update**. This means that a 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 function 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.
+
+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 them.
+
+## Can I upgrade Serverless Function resources (vCPU and RAM) at any time?
+
+Yes, Serverless Functions resources can be changed at any time without causing downtime, see the previous question for full details.
+
+## How do I integrate my serverless solutions with other Scaleway services?
+
+Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/serverless/messaging/concepts/#queues) and [Topics and Events](/serverless/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless/sql-databases/). [Serverless Jobs](/serverless/jobs/) can pull data from [Object Storage](/storage/object), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
+
 ## How am I billed for Serverless Functions?
 
 ### Principle
@@ -184,3 +219,27 @@ solutions like Scaleway Object Storage.
 
 Currently, a new function instance will always start after each deployment, even if there is no traffic and the minimum
 scale is set to 0. This behavior is not configurable at this time.
+
+## How can I store data in my Serverless resource?
+
+Serverless resources are by default [stateless](/serverless/functions/concepts/#stateless), local storage is ephemeral.
+
+For some use cases, such as saving analysis results, exporting data etc., it can be important to save data. Serverless resources can be connected to other resources from the Scaleway ecosystem for this purpose:
+
+### Databases
+
+* [Serverless Databases](/serverless/sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations.
+* [Managed MySQL / PostgreSQL](/managed-databases/postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
+* [Managed Database for Redis®](/managed-databases/redis/): Fully managed Redis®* in seconds.
+* [Managed MongoDB®](/managed-databases/mongodb/): Get the best of MongoDB® and Scaleway in one database.
+
+### Storage
+
+* [Object Storage](/storage/object/): Multi-AZ resilient object storage service ensuring high availability for your data.
+* [Scaleway Glacier](/storage/object/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
+
+<Message type="tip">
+Explore all Scaleway products in the console and select the right product for your use case.
+
+Some products are not listed but for example, on specific use cases Secret Manager can help you to store informations that requires versioning.
+</Message>

faq/serverless-jobs.mdx

@@ -10,9 +10,27 @@ category: serverless
 productIcon: ServerlessJobsProductIcon
 ---
 
-## What are Serverless Jobs?
+## What is serverless computing, and how does it differ from traditional cloud hosting?
 
-Scaleway Serverless Jobs is a fully managed service that enables efficient execution of batch computing workloads. It automates management tasks, allowing users to run large-scale batch jobs with ease.
+Serverless computing is a cloud execution model where the cloud provider dynamically manages the allocation of compute resources. Unlike traditional hosting models, you do not need to provision, scale, or maintain servers. Instead, you focus solely on writing and deploying your code, and the infrastructure scales automatically to meet demand.
+
+## Why consider using Serverless Containers, Functions, or Jobs for my projects?
+
+These services allow you to build highly scalable, event-driven, and pay-as-you-go solutions. Serverless Containers and Functions help you create applications and microservices without worrying about server management, while Serverless Jobs lets you run large-scale, parallel batch-processing tasks efficiently. This can lead to faster development cycles, reduced operational overhead, and cost savings.
+
+## What is Serverless Jobs, and when should I use it?
+
+Serverless Jobs allows you to run large-scale batch processing and computational workloads in a fully managed environment. If you have tasks like data processing, machine learning training jobs, simulations, or large-scale analytics that can be parallelized, Serverless Jobs helps you orchestrate and manage those workloads seamlessly.
+
+## How do I integrate my serverless solutions with other Scaleway services?
+
+Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/serverless/messaging/concepts/#queues) and [Topics and Events](/serverless/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless/sql-databases/). [Serverless Jobs](/serverless/jobs/) can pull data from [Object Storage](/storage/object), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
+
+## Can I update Serverless Jobs resources (vCPU and RAM) at any time?
+
+Yes, resources of your Job Definition can be updated at any time.
+
+Ongoing Job Runs will remain using the resources definied at the time it started.
 
 ## How am I billed for Serverless Jobs?
 
@@ -124,3 +142,26 @@ To add network restrictions on your resource, consult the [list of prefixes used
 ## Can I securely use sensitive information with Serverless Jobs?
 
 Yes, you can use sensitive data such as API secret keys, passwords, TLS/SSL certificates, or tokens. Serverless Jobs seamlessly integrates with [Secret Manager](/identity-and-access-management/secret-manager/), which allows you to securely reference sensitive information within your jobs. Refer to the [dedicated documentation](/serverless/jobs/how-to/reference-secret-in-job/) for more information.
+
+## How can I store data in my Serverless resource?
+
+Serverless resources are by default [stateless](/serverless/functions/concepts/#stateless), local storage is ephemeral.
+
+For some use cases, such as saving analysis results, exporting data etc., it can be important to save data. Serverless resources can be connected to other resources from the Scaleway ecosystem for this purpose:
+
+### Databases
+
+* [Serverless Databases](/serverless/sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations.
+* [Managed MySQL / PostgreSQL](/managed-databases/postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
+* [Managed MongoDB®](/managed-databases/mongodb/): Get the best of MongoDB® and Scaleway in one database.
+
+### Storage
+
+* [Object Storage](/storage/object/): Multi-AZ resilient object storage service ensuring high availability for your data.
+* [Scaleway Glacier](/storage/object/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
+
+<Message type="tip">
+Explore all Scaleway products in the console and select the right product for your use case.
+
+Some products are not listed but for example, on specific use cases Secret Manager can help you to store informations that requires versioning.
+</Message>