feat(serverless): update concepts

Author: thomas-tacquet

serverless/containers/concepts.mdx

@@ -43,7 +43,7 @@ Container Registry is the place where your images are stored before being deploy
 
 ## CRON trigger
 
-A CRON trigger is a mechanism used to automatically invoke a Serverless Function at a specific time on a recurring schedule.
+A CRON trigger is a mechanism used to automatically invoke a Serverless Container at a specific time on a recurring schedule.
 
 It works similarly to a traditional Linux [cron job](https://en.wikipedia.org/wiki/Cron), using the `* * * * *` format, and uses the **UTC** time zone. Refer to our [cron schedules reference](/serverless/containers/reference-content/cron-schedules/) for more information.
 
@@ -95,10 +95,18 @@ JWT (JSON Web Token) is an access token you can create from the console or API t
 
 The Serverless infrastructure manages incoming request traffic. In scenarios like sudden traffic spikes or load testing, resources are automatically scaled based on the max scale parameter to handle the load.
 
+## Logging
+
+Serverless offers a built-in logging system based on cockpit to follow the activity of your ressources: [monitoring Serverless Containers](/serverless/containers/how-to/monitor-container/).
+
 ## Max scale
 
 This parameter sets the maximum number of container instances. You should adjust it based on your container's traffic spikes, keeping in mind that you may wish to limit the max scale to manage costs effectively.
 
+## Metrics
+
+Performances of your Serverless ressources are natively available: [monitoring Serverless Containers](/serverless/containers/how-to/monitor-container/).
+
 ## Min scale
 
 Customizing the minimum scale for Serverless can help ensure that an instance remains pre-allocated and ready to handle requests, reducing delays associated with cold starts. However, this setting also impacts the costs of your Serverless Container.
@@ -160,6 +168,12 @@ 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
+
+A Serverless Function are serverless, 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 without worrying 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 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.
@@ -184,6 +198,14 @@ A Serverless Container can have the following statuses:
 * **Pending**: your resource is under deployment.
 * **Error**: something went wrong during the deployment process. [Check our troubleshooting documentation](/serverless/containers/troubleshooting/cannot-deploy-image) to solve the issue.
 
+## Stateless
+
+Refers to a system or application that does not maintain any persistent state between executions. In a stateless environment, each request or operation is independent, and no information is retained from previous interactions.
+
+This means that each request is treated as a new and isolated event, and there is no need for the system to remember previous states or data once a task is completed. Statelessness is commonly used in serverless architectures where each function execution is independent of others.
+
+To store informations you can use [Scaleway Object Storage](/storage/object/), [Scaleway Managed Databases](/managed-databases/postgresql-and-mysql/), [Scaleway Serverless Databases](/serverless/sql-databases/).
+
 ## Terraform
 
 Terraform is a tool for managing infrastructure using code. [Read the Terraform documentation for Serverless Containers](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/container).

serverless/functions/concepts.mdx

@@ -12,6 +12,12 @@ categories:
   - serverless
 ---
 
+## Build step
+
+Before deploying a Serverless Functions it has to be built, this step occurs on deployment.
+
+Once the Function is built into an image, it will be pushed to [Container Registry](#container-registry)
+
 ## Cold Start
 
 Cold Start is the time a function takes to handle a request when it is called for the first time.
@@ -23,33 +29,67 @@ Startup process steps are:
 
 [How to reduce cold starts](/faq/serverless-functions/#how-to-reduce-cold-start-of-serverless-functions)
 
+## Container Registry
+
+Container Registry is the place where your images of your Serverless Functions are stored before being deployed.
+
 ## CRON trigger
 
 A CRON trigger is a mechanism used to automatically invoke a Serverless Function at a specific time on a recurring schedule. It works similarly to a traditional Linux [cron job](https://en.wikipedia.org/wiki/Cron), using the `* * * * *` format, and uses the **UTC** time zone.  Refer to our [cron schedules reference](/serverless/functions/reference-content/cron-schedules/) for more information.
 
-## Environment variables
+## Custom domain
+
+By default, a generated endpoint is assigned to your Serverless resource. Custom domains allows you to use your own domain - see our [custom domain documentation](/serverless/functions/how-to/add-a-custom-domain-to-a-function) for full details.
 
-An environment variable is a variable whose value is set outside the program, typically through functionality built into the operating system or microservice. An environment variable is made up of a name/value pair, and any number may be created and available for reference at a point in time.
+## Endpoint
 
-## Function
+An endpoint is the URL generated to access your resource. It can be customized with [custom domains](#custom-domain).
 
-A function defines a procedure on how to change one element into another. The function remains static, while the variables that pass through it can vary.
+## Environment variables
+
+Environment variables are key/value pairs injected in your container. They are useful to share information such as configurations with your container. Some names are reserved. [See details about reserved names](/serverless/functions/reference-content/functions-limitations/#configuration-restrictions).
 
 ## GB-s
 
-Unit used to measure the resource consumption of a function. It reflects the amount of memory consumed over time.
+Unit used to measure the resource consumption of a Function. It reflects the amount of memory consumed over time.
 
 ## JWT Token
 
-A JWT (JSON Web Token) is an access token you can create from the console or the API to enable an application to access your Private function.
+JWT (JSON Web Token) is an access token you can create from the console or API to enable an application to access your private container. [Find out how to secure a Function](/serverless/functions/how-to/secure-a-function/#restrict-access-to-your-functions).
 
 ## Handler
 
 A handler is a routine/function/method that processes specific events. Upon invoking your function, the handler is executed and returns an output. Refer to our [dedicated documentation](/serverless/functions/reference-content/functions-handlers/) for more information on the structure of a handler.
 
+## Instance
+
+A Serverless Function instance handles incoming requests based on factors like the request volume, min scale, and max scale parameters.
+
+## Load balancing
+
+The Serverless infrastructure manages incoming request traffic. In scenarios like sudden traffic spikes or load testing, resources are automatically scaled based on the max scale parameter to handle the load.
+
+## Logging
+
+Serverless offers a built-in logging system based on cockpit to follow the activity of your ressources: [monitoring Serverless Functions](/serverless/functions/how-to/monitor-function/).
+
+## Max scale
+
+This parameter sets the maximum number of function instances. You should adjust it based on your function's traffic spikes, keeping in mind that you may wish to limit the max scale to manage costs effectively.
+
+## Metrics
+
+Performances of your Serverless ressources are natively available: [monitoring Serverless Functions](/serverless/functions/how-to/monitor-function/)).
+
+## Min scale
+
+Customizing the minimum scale for Serverless can help ensure that an instance remains pre-allocated and ready to handle requests, reducing delays associated with cold starts. However, this setting also impacts the costs of your Serverless Function.
+
 ## Namespace
 
-A namespace is a project that allows you to [group your functions](/serverless/functions/how-to/create-manage-delete-functions-namespace/). Functions in the same namespace can share environment variables and access tokens, defined at the namespace level.
+A namespace is a project that allows you to [group your functions](/serverless/functions/how-to/create-manage-delete-functions-namespace/).
+
+Functions in the same namespace can share environment variables and access tokens, defined at the namespace level.
 
 ## NATS trigger
 
@@ -62,6 +102,13 @@ The function can then process the message and perform any required actions, such
 
 A function's privacy policy defines whether a function may be executed anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-functions/#authentication) (**private**).
 
+## Queue trigger
+
+A queue trigger is a mechanism that connects a function to a queue created with [Scaleway Queues](/serverless/messaging/concepts/#queues), and invokes the function 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 function with the message as the input parameter.
+The function can then process the message and perform any required actions, such as updating a database or sending a notification.
+
 ## Runtime
 
 The runtime is the execution environment of your function. Regarding Serverless Function, it consists of the languages in which your code is written.
@@ -92,20 +139,31 @@ 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 Functions
+## Serverless Function
 
-Serverless Functions simplify deploying applications to the Cloud. They only require you to install a piece of business logic, a “function”, on any cloud platform, which executes it on demand. This allows you to focus on backend code without provisioning or maintaining servers.
+A Serverless Function are serverless, fully managed compute services that allow you to run small, stateless code snippets or functions in response to HTTP requests or events.
 
-The platform also handles function availability and manages resource allocation for you. For instance, if the system needs to accommodate 100 simultaneous requests, it allocates 100 (or more) copies of your service. If demand drops to two concurrent requests, it destroys the unneeded ones.
+These functions automatically scale based on demand and are designed to be lightweight, event-driven, and easily deployable without worrying 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.
 
-You pay for the resources your functions use, and only when your functions need them.
+## Serverless Job
 
-## Queue trigger
+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.
 
-A queue trigger is a mechanism that connects a function to a queue created with [Scaleway Queues](/serverless/messaging/concepts/#queues), and invokes the function automatically whenever a message is added to the queue.
+## Stateless
+
+Refers to a system or application that does not maintain any persistent state between executions. In a stateless environment, each request or operation is independent, and no information is retained from previous interactions.
+
+This means that each request is treated as a new and isolated event, and there is no need for the system to remember previous states or data once a task is completed. Statelessness is commonly used in serverless architectures where each function execution is independent of others.
+
+To store informations you can use [Scaleway Object Storage](/storage/object/), [Scaleway Managed Databases](/managed-databases/postgresql-and-mysql/), [Scaleway Serverless Databases](/serverless/sql-databases/).
+
+## Status
+
+A Serverless Function can have the following statuses:
+* **Ready**: your Serverless Function is operational to serve requests.
+* **Pending**: your resource is under deployment.
+* **Error**: something went wrong during the deployment process or build of the source code to image. [Check our troubleshooting documentation](/serverless/functions/troubleshooting/function-in-error-state/) to solve the issue.
 
-For each message that is sent to a queue, the trigger reads the message and invokes the associated function with the message as the input parameter.
-The function can then process the message and perform any required actions, such as updating a database or sending a notification.
 
 ## Timeout
 

serverless/jobs/concepts.mdx

@@ -12,10 +12,9 @@ categories:
   - serverless
 ---
 
-## Container image
+## Container Registry
 
-A container image is a file that includes all the requirements and instructions of a complete and executable version of an application. 
-When running a job, the selected image will be pulled to execute your workload. Images can come from public external registries or from the [Scaleway Container Registry](/containers/container-registry/concepts/#container-registry).
+Container Registry is the place where your images are stored before being deployed, we recommend using Scaleway Container Registry for optimal integration. [Migration guide](/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry/).
 
 ## Environment variables
 
@@ -45,22 +44,46 @@ The name of a job is part of the [job definition](#job-definition) and is used f
 
 A job run is the execution of a job definition. It can be in a running, succeeded, canceled, or failed status. Each job run has a unique identifier and can be individually monitored using [Cockpit](/observability/cockpit/quickstart/).
 
+## Logging
+
+Serverless offers a built-in logging system based on cockpit to follow the activity of your ressources: [monitoring Serverless Jobs](/serverless/jobs/how-to/monitor-job/).
+
 ## Maximum duration
 
 The maximum duration option allows you to define the maximum execution time before your job is automatically killed.
 
+## Metrics
+
+Performances of your Serverless ressources are natively available: [monitoring Serverless Jobs](/serverless/jobs/how-to/monitor-job/).
+
 ## Schedule (cron)
 
 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.
 
 ## Secrets reference
 
-A secret reference is a mechanism that allows you to use a secret stored in [Secret Manager](/identity-and-access-management/secret-manager/) within Serverless Jobs. It allows you to securely reference sensitive data, such as API secret keys, passwords, tokens, or certificates. 
+A secret reference is a mechanism that allows you to use a secret stored in [Secret Manager](/identity-and-access-management/secret-manager/) within Serverless Jobs. It allows you to securely reference sensitive data, such as API secret keys, passwords, tokens, or certificates.
 
 ## Startup command
 
 This optional field allows you to specify a custom command executed upon starting your job if your container image does not have one already, or if you use a public container image.
 
+## Status
+
+A Serverless Job Run can have the following statuses:
+* **Succeeded**: your Serverless Job Run finished in a good state.
+* **Queued**: your Serverless Job Run is waiting for ressources to run.
+* **Error**: your Serverless Job Run finished with an error or timeout. [Check our troubleshooting documentation](/serverless/jobs/troubleshooting/job-in-error-state/) to solve the issue.
+* **Canceled**: your Serverless Job Run has been canceled by the user.
+
+## Stateless
+
+Refers to a system or application that does not maintain any persistent state between executions. In a stateless environment, each request or operation is independent, and no information is retained from previous interactions.
+
+This means that each request is treated as a new and isolated event, and there is no need for the system to remember previous states or data once a task is completed. Statelessness is commonly used in serverless architectures where each function execution is independent of others.
+
+To store informations you can use [Scaleway Object Storage](/storage/object/), [Scaleway Managed Databases](/managed-databases/postgresql-and-mysql/), [Scaleway Serverless Databases](/serverless/sql-databases/).
+
 ## vCPU-s
 
 Unit used to measure the resource consumption of a container. It reflects the amount of vCPU used over time.