From a1857a72a609922d21f2387ae299a6dcbd11dd15 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Mon, 25 Aug 2025 14:51:07 +0200 Subject: [PATCH 1/6] docs(srv): add migration guide for serverless containers MTA-6412 --- .../migrate-to-serverless-containers.mdx | 86 +++++++++++++++++++ 1 file changed, 86 insertions(+) create mode 100644 pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx diff --git a/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx new file mode 100644 index 0000000000..7ca8a8333f --- /dev/null +++ b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx @@ -0,0 +1,86 @@ +--- +title: How to migrate your workloads to Scaleway Serverless Containers +description: This page gives recommendations and steps to migrate your workloads from Kubernetes or conventional virtual machines to Scaleway Serverless Containers +tags: migration switch change adopt serverless containers go serverless try k8s vm +dates: + validation: 2025-08-25 + posted: 2025-08-25 +--- + +This guide is designed for developers and operators who are currently running workloads on Kubernetes or traditional virtual machines and are considering a migration to [Serverless Containers](/serverless-containers/concepts/#serverless-containers). This guide covers the [core concepts](#why-migrating-to-serverless-containers) of Serverless Containers, the [operational benefits](#key-features) of this model, and a [practical path](#quick-deployment-guide) for migration. + +## Why migrating to Serverless Containers + +Moving to a Serverless Containers model involves a shift in operational responsibility from you to the cloud provider. This change brings several key advantages for development teams. + +- **Reduced operational overhead**: The primary benefit is the abstraction of the underlying infrastructure. You do not need to provision, manage, scale, or patch servers, operating systems, or container orchestration platforms like Kubernetes. This allows your team to focus on application logic rather than infrastructure management. + +- **Container-based workflow**: You can continue to use the standard container-based development workflow. Packaging your application and its dependencies into a container image ensures a consistent and reproducible environment, from local development to production. + +- **Stateless architecture**: Serverless Containers are designed for stateless services. This architectural pattern promotes building applications that are horizontally scalable and resilient, as any instance can handle any request without relying on local state. + +- **Efficient resource consumption**: The platform automatically scales the number of running container instances based on request volume, CPU consumption or RAM usage. This removes the need to manually configure and tune autoscaling rules, ensuring your application has the resources it needs to meet demand. For services with variable or infrequent traffic, this model is highly efficient, as resources can scale down to zero when there are no requests, eliminating the cost of idle capacity. + +Refer to our [dedicated overview page](/serverless-containers/reference-content/serverless-overview/) for general information on Scaleway's Serverless products. + +## Key features + +Serverless Containers come packed with features designed for modern application development: + +Private Network compatibility: Securely connect your services to other resources within your private cloud network. Read more about private networks integration (https://www.scaleway.com/en/docs/serverless-containers/reference-content/containers-private-networks/) + +Custom domains: Easily map your own domain names to your services. Check on how to add custom domains to Serverless Containers (https://www.scaleway.com/en/docs/serverless-containers/how-to/add-a-custom-domain-to-a-container/) + +Healthchecks: Configure readiness and liveness probes to ensure your application instances are healthy and ready to serve traffic. Get more info about healtchecks (https://www.scaleway.com/en/docs/serverless-containers/concepts/#health-check) + +Built-in monitoring: Gain immediate insights into your application's performance with integrated logging and metrics, without needing to set up complex monitoring agents. Check how to monitor your Serverless Container (https://www.scaleway.com/en/docs/serverless-containers/how-to/monitor-container/) + +Enhanced security: Because the platform is managed by the cloud provider, it benefits from continuous security patching and best practices, reducing your operational security burden. Check how to secure a Serverless Container (https://www.scaleway.com/en/docs/serverless-containers/how-to/secure-a-container/) + +For additional features related to Serverless Containers, check for all Concepts (https://www.scaleway.com/en/docs/serverless-containers/concepts/) + +## Quick deployment guide + +Deploying your first service to Serverless Containers is straightforward. Here’s a high-level overview of the steps: + +Containerize your Application: If you haven't already, package your application into a container image using a Dockerfile. Read Container Registry quickstart(https://www.scaleway.com/en/docs/container-registry/quickstart/) + +Push to a Registry: Push your container image to Scaleway Container Registry. + +Deploy a container: Read How to deploy a Container](https://www.scaleway.com/en/docs/serverless-containers/how-to/deploy-container/) + +Deploy: Click "Deploy" and the platform will pull your container image and run it. Within minutes, you'll have a publicly accessible HTTPS endpoint for your new service. + +Best practices for migration + +Migrating existing applications from Kubernetes or Instances to Serverless Containers is an opportunity to modernize your architecture. + +General best practices + +Containerize everything: Your application must be packaged as a container image. This is the fundamental deployment unit for Serverless Containers + +Embrace statelessness: Since Serverless Containers are stateless, you cannot rely on the local filesystem for storing data that needs to persist between requests + +Use external storage: For file storage, use an object storage service like Scaleway Object Storage (https://www.scaleway.com/en/docs/object-storage/quickstart/) + +Externalize state: For application state, use a managed database, cache like Redis(https://www.scaleway.com/en/docs/managed-databases-for-redis/how-to/create-a-database-for-redis/) or a message queues(https://www.scaleway.com/en/docs/queues/quickstart/) + +Manage your infrastructure as code: While you can manage your services through the console, we highly recommend using developer tools for a repeatable and version-controlled setup. + +CLI: Use the command-line interface provided by your cloud provider for scripting and automation. Read more(https://www.scaleway.com/en/docs/scaleway-cli/quickstart/) + +Terraform/IaC: Define your Serverless Containers services using tools like Terraform for a fully automated and declarative infrastructure. Read more (https://www.scaleway.com/en/docs/terraform/quickstart/) + +Migration Strategies + +Progressive migration: You don't need to migrate your entire application at once. Serverless Containers are perfect for microservices. You can start by migrating a single, smaller service to get a feel for the platform. This approach minimizes risk and allows your team to learn as you go. + +API Migration: When migrating an API, you can create a new version of your API on Serverless Containers. For example, you can create a new /v2/ endpoint for your API that is served by Serverless Containers, while the existing /v1/ remains on your current infrastructure. This allows for a gradual rollout to your users. + +Start small with Serverless Jobs + +If you're looking for an even simpler way to start your Serverless journey, consider using Serverless Jobs. This is a companion product designed for running batch jobs, scripts, or automated tasks that run to completion. + +Instead of migrating a full web service, you can start by offloading a small automation task (like a nightly data processing script) to a Serverless Job. This is a low-risk way to familiarize your team with the serverless container ecosystem before committing to migrating larger, more critical services. + +Quickstart of Serverless Jobs product (https://www.scaleway.com/en/docs/serverless-jobs/quickstart/) \ No newline at end of file From fd231b3b34b1f22f5d2e7ea41efe28311b3e6e0e Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Tue, 26 Aug 2025 17:50:13 +0200 Subject: [PATCH 2/6] docs(srv): update --- menu/navigation.json | 4 + .../migrate-to-serverless-containers.mdx | 81 ++++++++++++------- 2 files changed, 58 insertions(+), 27 deletions(-) diff --git a/menu/navigation.json b/menu/navigation.json index 9adb842ca4..5425b1111e 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -4579,6 +4579,10 @@ "label": "Serverless overview", "slug": "serverless-overview" }, + { + "label": "Migrating to Serverless Containers", + "slug": "migrate-to-serverless-containers" + }, { "label": "Containers and Private Networks integration", "slug": "containers-private-networks" diff --git a/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx index 7ca8a8333f..599334ac98 100644 --- a/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx +++ b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx @@ -13,65 +13,92 @@ This guide is designed for developers and operators who are currently running wo Moving to a Serverless Containers model involves a shift in operational responsibility from you to the cloud provider. This change brings several key advantages for development teams. -- **Reduced operational overhead**: The primary benefit is the abstraction of the underlying infrastructure. You do not need to provision, manage, scale, or patch servers, operating systems, or container orchestration platforms like Kubernetes. This allows your team to focus on application logic rather than infrastructure management. +**Reduced operational overhead** -- **Container-based workflow**: You can continue to use the standard container-based development workflow. Packaging your application and its dependencies into a container image ensures a consistent and reproducible environment, from local development to production. +The primary benefit is the abstraction of the underlying infrastructure. You do not need to provision, manage, scale, or patch servers, operating systems, or container orchestration platforms like Kubernetes. This allows your team to focus on application logic rather than infrastructure management. -- **Stateless architecture**: Serverless Containers are designed for stateless services. This architectural pattern promotes building applications that are horizontally scalable and resilient, as any instance can handle any request without relying on local state. +**Container-based workflow** -- **Efficient resource consumption**: The platform automatically scales the number of running container instances based on request volume, CPU consumption or RAM usage. This removes the need to manually configure and tune autoscaling rules, ensuring your application has the resources it needs to meet demand. For services with variable or infrequent traffic, this model is highly efficient, as resources can scale down to zero when there are no requests, eliminating the cost of idle capacity. +You can continue to use the standard container-based development workflow. Packaging your application and its dependencies into a container image ensures a consistent and reproducible environment, from local development to production. + +**Stateless architecture** + +Serverless Containers are designed for stateless services. This architectural pattern promotes building applications that are horizontally scalable and resilient, as any instance can handle any request without relying on local state. + +**Efficient resource consumption** + +The platform automatically scales the number of running container instances based on request volume, CPU consumption or RAM usage. This removes the need to manually configure and tune autoscaling rules, ensuring your application has the resources it needs to meet demand. For services with variable or infrequent traffic, this model is highly efficient, as resources can scale down to zero when there are no requests, eliminating the cost of idle capacity. Refer to our [dedicated overview page](/serverless-containers/reference-content/serverless-overview/) for general information on Scaleway's Serverless products. ## Key features -Serverless Containers come packed with features designed for modern application development: +Serverless Containers come packed with features designed for modern application development. -Private Network compatibility: Securely connect your services to other resources within your private cloud network. Read more about private networks integration (https://www.scaleway.com/en/docs/serverless-containers/reference-content/containers-private-networks/) +- **Private Networks compatibility**: Securely connect your services to other resources within your Virtual Private Cloud. + - Learn [how to use Private Networks with Serverless Containers](/serverless-containers/reference-content/containers-private-networks/). -Custom domains: Easily map your own domain names to your services. Check on how to add custom domains to Serverless Containers (https://www.scaleway.com/en/docs/serverless-containers/how-to/add-a-custom-domain-to-a-container/) +- **Custom domains**: Easily map your own domain names to your services. + - Discover [how to add custom domains to Serverless Containers](/serverless-containers/how-to/add-a-custom-domain-to-a-container/). -Healthchecks: Configure readiness and liveness probes to ensure your application instances are healthy and ready to serve traffic. Get more info about healtchecks (https://www.scaleway.com/en/docs/serverless-containers/concepts/#health-check) +- **Healthchecks**: Configure readiness and liveness probes to ensure your application instances are healthy and ready to serve traffic. + - Get [information about healtchecks](/serverless-containers/concepts/#health-check). -Built-in monitoring: Gain immediate insights into your application's performance with integrated logging and metrics, without needing to set up complex monitoring agents. Check how to monitor your Serverless Container (https://www.scaleway.com/en/docs/serverless-containers/how-to/monitor-container/) +- **Built-in monitoring**: Gain immediate insights on your application's performance with integrated logging and metrics, without needing to set up complex monitoring agents. + - Check [how to monitor your Serverless Container](/serverless-containers/how-to/monitor-container/). -Enhanced security: Because the platform is managed by the cloud provider, it benefits from continuous security patching and best practices, reducing your operational security burden. Check how to secure a Serverless Container (https://www.scaleway.com/en/docs/serverless-containers/how-to/secure-a-container/) +- **Enhanced security**: Because the platform is managed by Scaleway, it benefits from continuous security patching and best practices, reducing your operational security burden. + - Find out [how to secure a Serverless Container](/serverless-containers/how-to/secure-a-container/). -For additional features related to Serverless Containers, check for all Concepts (https://www.scaleway.com/en/docs/serverless-containers/concepts/) +To dive deeper into Serverless Containers, refer to the dedicated [Concepts page](/serverless-containers/concepts/). ## Quick deployment guide -Deploying your first service to Serverless Containers is straightforward. Here’s a high-level overview of the steps: +Deploying your first service to Serverless Containers is straightforward. Here’s a high-level overview of the steps. -Containerize your Application: If you haven't already, package your application into a container image using a Dockerfile. Read Container Registry quickstart(https://www.scaleway.com/en/docs/container-registry/quickstart/) +1. **Containerize your Application**: If you haven't already, package your application into a container image using a Dockerfile. -Push to a Registry: Push your container image to Scaleway Container Registry. +2. **Push your image to a Registry**: Follow the [dedicated Quickstart documenation](/container-registry/quickstart/) to push your container image to the Scaleway Container Registry. -Deploy a container: Read How to deploy a Container](https://www.scaleway.com/en/docs/serverless-containers/how-to/deploy-container/) +3. **Deploy your container**: Read the [How to deploy a container](/serverless-containers/how-to/deploy-container/) page to create your container using the Scaleway Console. -Deploy: Click "Deploy" and the platform will pull your container image and run it. Within minutes, you'll have a publicly accessible HTTPS endpoint for your new service. +4. **Click Deploy**: the Scaleway platform will pull your container image and run it. Within a few minutes, your Serverless Container will be publicly accessible via its HTTPS endpoint. -Best practices for migration +## Best practices for migration Migrating existing applications from Kubernetes or Instances to Serverless Containers is an opportunity to modernize your architecture. -General best practices +### General best practices + +**Containerize everything** + +Your application must be packaged as a container image. This is the fundamental deployment unit for Serverless Containers. + +**Embrace statelessness** + +Since Serverless Containers are stateless, you cannot rely on the local filesystem for storing data that needs to persist between requests + +**Use external storage** + +For file storage, use an object storage service like Scaleway Object Storage (/object-storage/quickstart/) + +**Externalize state** -Containerize everything: Your application must be packaged as a container image. This is the fundamental deployment unit for Serverless Containers +For application state, use a managed database, cache like Redis(/managed-databases-for-redis/how-to/create-a-database-for-redis/) or a message queues(/queues/quickstart/) -Embrace statelessness: Since Serverless Containers are stateless, you cannot rely on the local filesystem for storing data that needs to persist between requests +**Manage your infrastructure as code** -Use external storage: For file storage, use an object storage service like Scaleway Object Storage (https://www.scaleway.com/en/docs/object-storage/quickstart/) +While you can manage your services through the console, we highly recommend using developer tools for a repeatable and version-controlled setup. -Externalize state: For application state, use a managed database, cache like Redis(https://www.scaleway.com/en/docs/managed-databases-for-redis/how-to/create-a-database-for-redis/) or a message queues(https://www.scaleway.com/en/docs/queues/quickstart/) +**CLI** -Manage your infrastructure as code: While you can manage your services through the console, we highly recommend using developer tools for a repeatable and version-controlled setup. +Use the command-line interface provided by your cloud provider for scripting and automation. Read more(/scaleway-cli/quickstart/) -CLI: Use the command-line interface provided by your cloud provider for scripting and automation. Read more(https://www.scaleway.com/en/docs/scaleway-cli/quickstart/) +**Terraform/IaC** -Terraform/IaC: Define your Serverless Containers services using tools like Terraform for a fully automated and declarative infrastructure. Read more (https://www.scaleway.com/en/docs/terraform/quickstart/) +Define your Serverless Containers services using tools like Terraform for a fully automated and declarative infrastructure. Read more (/terraform/quickstart/) -Migration Strategies +## Migration Strategies Progressive migration: You don't need to migrate your entire application at once. Serverless Containers are perfect for microservices. You can start by migrating a single, smaller service to get a feel for the platform. This approach minimizes risk and allows your team to learn as you go. @@ -83,4 +110,4 @@ If you're looking for an even simpler way to start your Serverless journey, cons Instead of migrating a full web service, you can start by offloading a small automation task (like a nightly data processing script) to a Serverless Job. This is a low-risk way to familiarize your team with the serverless container ecosystem before committing to migrating larger, more critical services. -Quickstart of Serverless Jobs product (https://www.scaleway.com/en/docs/serverless-jobs/quickstart/) \ No newline at end of file +Quickstart of Serverless Jobs product (/serverless-jobs/quickstart/) \ No newline at end of file From 2f7f0e6bf372f1cc0c9314dca5277a2e2c62ee57 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 27 Aug 2025 11:09:13 +0200 Subject: [PATCH 3/6] docs(srv): update --- .../migrate-to-serverless-containers.mdx | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx index 599334ac98..ff29745374 100644 --- a/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx +++ b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx @@ -100,14 +100,18 @@ Define your Serverless Containers services using tools like Terraform for a full ## Migration Strategies -Progressive migration: You don't need to migrate your entire application at once. Serverless Containers are perfect for microservices. You can start by migrating a single, smaller service to get a feel for the platform. This approach minimizes risk and allows your team to learn as you go. +**Progressive migration** -API Migration: When migrating an API, you can create a new version of your API on Serverless Containers. For example, you can create a new /v2/ endpoint for your API that is served by Serverless Containers, while the existing /v1/ remains on your current infrastructure. This allows for a gradual rollout to your users. +You do not need to migrate your entire application at once. Serverless Containers are perfect for microservices. You can start by migrating a single, smaller service to get a feel of the platform. This approach minimizes risk and allows your teams to learn as they go. -Start small with Serverless Jobs +**API Migration** -If you're looking for an even simpler way to start your Serverless journey, consider using Serverless Jobs. This is a companion product designed for running batch jobs, scripts, or automated tasks that run to completion. +When migrating an API, you can create a new version of your API on Serverless Containers. For example, you can create a new /v2/ endpoint for your API that is served by Serverless Containers, while the existing /v1/ remains on your current infrastructure. This allows for a gradual rollout to your users. + +## Start small with Serverless Jobs + +If you're looking for an even simpler way to start your Serverless journey, consider using Serverless Jobs. This is a companion product designed for running autonomous batch jobs, scripts, or automated tasks that run to completion. Instead of migrating a full web service, you can start by offloading a small automation task (like a nightly data processing script) to a Serverless Job. This is a low-risk way to familiarize your team with the serverless container ecosystem before committing to migrating larger, more critical services. -Quickstart of Serverless Jobs product (/serverless-jobs/quickstart/) \ No newline at end of file +Refer to the [Serverless Jobs quickstart guide](/serverless-jobs/quickstart/) to deploy your first job in a few minutes. From af41f09bee95729980c7116c1b4c79c7a5fa4bcd Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 27 Aug 2025 11:42:28 +0200 Subject: [PATCH 4/6] docs(srv): update --- .../migrate-to-serverless-containers.mdx | 24 ++++++++++--------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx index ff29745374..c72433524f 100644 --- a/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx +++ b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx @@ -3,11 +3,13 @@ title: How to migrate your workloads to Scaleway Serverless Containers description: This page gives recommendations and steps to migrate your workloads from Kubernetes or conventional virtual machines to Scaleway Serverless Containers tags: migration switch change adopt serverless containers go serverless try k8s vm dates: - validation: 2025-08-25 - posted: 2025-08-25 + validation: 2025-08-27 + posted: 2025-08-27 --- -This guide is designed for developers and operators who are currently running workloads on Kubernetes or traditional virtual machines and are considering a migration to [Serverless Containers](/serverless-containers/concepts/#serverless-containers). This guide covers the [core concepts](#why-migrating-to-serverless-containers) of Serverless Containers, the [operational benefits](#key-features) of this model, and a [practical path](#quick-deployment-guide) for migration. +This guide is designed for developers and operators who are currently running workloads on Kubernetes or traditional virtual machines, and are considering a migration to [Serverless Containers](/serverless-containers/concepts/#serverless-containers). + +This guide covers the [core concepts](#why-migrating-to-serverless-containers) of Serverless Containers, the [operational benefits](#key-features) of this model, and a [practical path](#quick-deployment-guide) for migration. ## Why migrating to Serverless Containers @@ -58,7 +60,7 @@ Deploying your first service to Serverless Containers is straightforward. Here 1. **Containerize your Application**: If you haven't already, package your application into a container image using a Dockerfile. -2. **Push your image to a Registry**: Follow the [dedicated Quickstart documenation](/container-registry/quickstart/) to push your container image to the Scaleway Container Registry. +2. **Push your image to a Registry**: Follow the [dedicated Quickstart documenation](/container-registry/quickstart/) to discover how to log in to the Scaleway Container Registry and store your images. 3. **Deploy your container**: Read the [How to deploy a container](/serverless-containers/how-to/deploy-container/) page to create your container using the Scaleway Console. @@ -80,11 +82,11 @@ Since Serverless Containers are stateless, you cannot rely on the local filesyst **Use external storage** -For file storage, use an object storage service like Scaleway Object Storage (/object-storage/quickstart/) +To store data you can use [Scaleway Object Storage](/object-storage/), [Scaleway Managed Databases](/managed-databases-for-postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless-sql-databases/). **Externalize state** -For application state, use a managed database, cache like Redis(/managed-databases-for-redis/how-to/create-a-database-for-redis/) or a message queues(/queues/quickstart/) +For application state, use a managed database, cache like [Redis](/managed-databases-for-redis/how-to/create-a-database-for-redis/) or [message queues](/queues/quickstart/). **Manage your infrastructure as code** @@ -92,13 +94,13 @@ While you can manage your services through the console, we highly recommend usin **CLI** -Use the command-line interface provided by your cloud provider for scripting and automation. Read more(/scaleway-cli/quickstart/) +Use the [Scaleway command-line interface](/scaleway-cli/quickstart/) for easy resources management, scripting, and automation. **Terraform/IaC** -Define your Serverless Containers services using tools like Terraform for a fully automated and declarative infrastructure. Read more (/terraform/quickstart/) +Define your Serverless Containers services using tools like Terraform or OpenTofu via the [Scaleway Provider](/terraform/quickstart/) for a fully automated and declarative infrastructure. -## Migration Strategies +### Migration Strategies **Progressive migration** @@ -106,9 +108,9 @@ You do not need to migrate your entire application at once. Serverless Container **API Migration** -When migrating an API, you can create a new version of your API on Serverless Containers. For example, you can create a new /v2/ endpoint for your API that is served by Serverless Containers, while the existing /v1/ remains on your current infrastructure. This allows for a gradual rollout to your users. +When migrating an API, you can create a new version of your API on Serverless Containers. For example, you can create a new `/v2/` endpoint for your API that is served by Serverless Containers, while the existing `/v1/` remains on your current infrastructure. This allows for a gradual rollout to your users. -## Start small with Serverless Jobs +### Start small with Serverless Jobs If you're looking for an even simpler way to start your Serverless journey, consider using Serverless Jobs. This is a companion product designed for running autonomous batch jobs, scripts, or automated tasks that run to completion. From ba01134250efe715b44a798a3aef0d623d19d448 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Fri, 29 Aug 2025 13:37:52 +0200 Subject: [PATCH 5/6] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Néda <87707325+nerda-codes@users.noreply.github.com> Co-authored-by: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> --- .../migrate-to-serverless-containers.mdx | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx index c72433524f..433af1fe57 100644 --- a/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx +++ b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx @@ -9,9 +9,9 @@ dates: This guide is designed for developers and operators who are currently running workloads on Kubernetes or traditional virtual machines, and are considering a migration to [Serverless Containers](/serverless-containers/concepts/#serverless-containers). -This guide covers the [core concepts](#why-migrating-to-serverless-containers) of Serverless Containers, the [operational benefits](#key-features) of this model, and a [practical path](#quick-deployment-guide) for migration. +This guide covers the [core concepts](#why-migrate-to-serverless-containers) of Serverless Containers, the [operational benefits](#key-features) of this model, and a [practical path](#quick-deployment-guide) for migration. -## Why migrating to Serverless Containers +## Why migrate to Serverless Containers Moving to a Serverless Containers model involves a shift in operational responsibility from you to the cloud provider. This change brings several key advantages for development teams. @@ -52,19 +52,19 @@ Serverless Containers come packed with features designed for modern application - **Enhanced security**: Because the platform is managed by Scaleway, it benefits from continuous security patching and best practices, reducing your operational security burden. - Find out [how to secure a Serverless Container](/serverless-containers/how-to/secure-a-container/). -To dive deeper into Serverless Containers, refer to the dedicated [Concepts page](/serverless-containers/concepts/). +To dive deeper into Serverless Containers, refer to the dedicated [concepts page](/serverless-containers/concepts/). ## Quick deployment guide Deploying your first service to Serverless Containers is straightforward. Here’s a high-level overview of the steps. -1. **Containerize your Application**: If you haven't already, package your application into a container image using a Dockerfile. +1. **Containerize your application**: If you haven't already, package your application into a container image using a Dockerfile. -2. **Push your image to a Registry**: Follow the [dedicated Quickstart documenation](/container-registry/quickstart/) to discover how to log in to the Scaleway Container Registry and store your images. +2. **Push your image to a registry**: Follow the [dedicated Quickstart documenation](/container-registry/quickstart/) to discover how to log in to the Scaleway Container Registry and store your images. -3. **Deploy your container**: Read the [How to deploy a container](/serverless-containers/how-to/deploy-container/) page to create your container using the Scaleway Console. +3. **Deploy your container**: Read the [How to deploy a container](/serverless-containers/how-to/deploy-container/) page to create your container using the Scaleway console. -4. **Click Deploy**: the Scaleway platform will pull your container image and run it. Within a few minutes, your Serverless Container will be publicly accessible via its HTTPS endpoint. +4. **Click Deploy**: The Scaleway platform will pull your container image and run it. Within a few minutes, your Serverless Container will be publicly accessible via its HTTPS endpoint. ## Best practices for migration @@ -82,7 +82,7 @@ Since Serverless Containers are stateless, you cannot rely on the local filesyst **Use external storage** -To store data you can use [Scaleway Object Storage](/object-storage/), [Scaleway Managed Databases](/managed-databases-for-postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless-sql-databases/). +To store data, you can use [Scaleway Object Storage](/object-storage/), [Scaleway Managed Databases](/managed-databases-for-postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless-sql-databases/). **Externalize state** @@ -90,30 +90,30 @@ For application state, use a managed database, cache like [Redis](/managed-datab **Manage your infrastructure as code** -While you can manage your services through the console, we highly recommend using developer tools for a repeatable and version-controlled setup. +While you can manage your services through the Scaleway console, we highly recommend using developer tools for a repeatable and version-controlled setup. **CLI** -Use the [Scaleway command-line interface](/scaleway-cli/quickstart/) for easy resources management, scripting, and automation. +Use the [Scaleway command-line interface](/scaleway-cli/quickstart/) for easy resource management, scripting, and automation. **Terraform/IaC** Define your Serverless Containers services using tools like Terraform or OpenTofu via the [Scaleway Provider](/terraform/quickstart/) for a fully automated and declarative infrastructure. -### Migration Strategies +### Migration strategies **Progressive migration** You do not need to migrate your entire application at once. Serverless Containers are perfect for microservices. You can start by migrating a single, smaller service to get a feel of the platform. This approach minimizes risk and allows your teams to learn as they go. -**API Migration** +**API migration** When migrating an API, you can create a new version of your API on Serverless Containers. For example, you can create a new `/v2/` endpoint for your API that is served by Serverless Containers, while the existing `/v1/` remains on your current infrastructure. This allows for a gradual rollout to your users. ### Start small with Serverless Jobs -If you're looking for an even simpler way to start your Serverless journey, consider using Serverless Jobs. This is a companion product designed for running autonomous batch jobs, scripts, or automated tasks that run to completion. +If you are looking for an even simpler way to start your Serverless journey, consider using Serverless Jobs. This is a companion product designed for running autonomous batch jobs, scripts, or automated tasks that run to completion. -Instead of migrating a full web service, you can start by offloading a small automation task (like a nightly data processing script) to a Serverless Job. This is a low-risk way to familiarize your team with the serverless container ecosystem before committing to migrating larger, more critical services. +Instead of migrating a full web service, you can start by offloading a small automation task (like a nightly data processing script) to a Serverless Job. This is a low-risk way to familiarize your team with the Serverless Container ecosystem before committing to migrating larger, more critical services. Refer to the [Serverless Jobs quickstart guide](/serverless-jobs/quickstart/) to deploy your first job in a few minutes. From 1c4d86498e824e3fee8e9e441319bac1bb69636d Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Fri, 29 Aug 2025 16:00:46 +0200 Subject: [PATCH 6/6] Update pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- .../reference-content/migrate-to-serverless-containers.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx index 433af1fe57..100e633fdd 100644 --- a/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx +++ b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx @@ -78,7 +78,7 @@ Your application must be packaged as a container image. This is the fundamental **Embrace statelessness** -Since Serverless Containers are stateless, you cannot rely on the local filesystem for storing data that needs to persist between requests +Since Serverless Containers are stateless, you cannot rely on the local filesystem for storing data that needs to persist between requests. **Use external storage**