|
| 1 | +--- |
| 2 | +title: How to migrate your workloads to Scaleway Serverless Containers |
| 3 | +description: This page gives recommendations and steps to migrate your workloads from Kubernetes or conventional virtual machines to Scaleway Serverless Containers |
| 4 | +tags: migration switch change adopt serverless containers go serverless try k8s vm |
| 5 | +dates: |
| 6 | + validation: 2025-08-27 |
| 7 | + posted: 2025-08-27 |
| 8 | +--- |
| 9 | + |
| 10 | +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). |
| 11 | + |
| 12 | +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. |
| 13 | + |
| 14 | +## Why migrate to Serverless Containers |
| 15 | + |
| 16 | +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. |
| 17 | + |
| 18 | +**Reduced operational overhead** |
| 19 | + |
| 20 | +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. |
| 21 | + |
| 22 | +**Container-based workflow** |
| 23 | + |
| 24 | +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. |
| 25 | + |
| 26 | +**Stateless architecture** |
| 27 | + |
| 28 | +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. |
| 29 | + |
| 30 | +**Efficient resource consumption** |
| 31 | + |
| 32 | +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. |
| 33 | + |
| 34 | +Refer to our [dedicated overview page](/serverless-containers/reference-content/serverless-overview/) for general information on Scaleway's Serverless products. |
| 35 | + |
| 36 | +## Key features |
| 37 | + |
| 38 | +Serverless Containers come packed with features designed for modern application development. |
| 39 | + |
| 40 | +- **Private Networks compatibility**: Securely connect your services to other resources within your Virtual Private Cloud. |
| 41 | + - Learn [how to use Private Networks with Serverless Containers](/serverless-containers/reference-content/containers-private-networks/). |
| 42 | + |
| 43 | +- **Custom domains**: Easily map your own domain names to your services. |
| 44 | + - Discover [how to add custom domains to Serverless Containers](/serverless-containers/how-to/add-a-custom-domain-to-a-container/). |
| 45 | + |
| 46 | +- **Healthchecks**: Configure readiness and liveness probes to ensure your application instances are healthy and ready to serve traffic. |
| 47 | + - Get [information about healtchecks](/serverless-containers/concepts/#health-check). |
| 48 | + |
| 49 | +- **Built-in monitoring**: Gain immediate insights on your application's performance with integrated logging and metrics, without needing to set up complex monitoring agents. |
| 50 | + - Check [how to monitor your Serverless Container](/serverless-containers/how-to/monitor-container/). |
| 51 | + |
| 52 | +- **Enhanced security**: Because the platform is managed by Scaleway, it benefits from continuous security patching and best practices, reducing your operational security burden. |
| 53 | + - Find out [how to secure a Serverless Container](/serverless-containers/how-to/secure-a-container/). |
| 54 | + |
| 55 | +To dive deeper into Serverless Containers, refer to the dedicated [concepts page](/serverless-containers/concepts/). |
| 56 | + |
| 57 | +## Quick deployment guide |
| 58 | + |
| 59 | +Deploying your first service to Serverless Containers is straightforward. Here’s a high-level overview of the steps. |
| 60 | + |
| 61 | +1. **Containerize your application**: If you haven't already, package your application into a container image using a Dockerfile. |
| 62 | + |
| 63 | +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. |
| 64 | + |
| 65 | +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. |
| 66 | + |
| 67 | +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. |
| 68 | + |
| 69 | +## Best practices for migration |
| 70 | + |
| 71 | +Migrating existing applications from Kubernetes or Instances to Serverless Containers is an opportunity to modernize your architecture. |
| 72 | + |
| 73 | +### General best practices |
| 74 | + |
| 75 | +**Containerize everything** |
| 76 | + |
| 77 | +Your application must be packaged as a container image. This is the fundamental deployment unit for Serverless Containers. |
| 78 | + |
| 79 | +**Embrace statelessness** |
| 80 | + |
| 81 | +Since Serverless Containers are stateless, you cannot rely on the local filesystem for storing data that needs to persist between requests. |
| 82 | + |
| 83 | +**Use external storage** |
| 84 | + |
| 85 | +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/). |
| 86 | + |
| 87 | +**Externalize state** |
| 88 | + |
| 89 | +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/). |
| 90 | + |
| 91 | +**Manage your infrastructure as code** |
| 92 | + |
| 93 | +While you can manage your services through the Scaleway console, we highly recommend using developer tools for a repeatable and version-controlled setup. |
| 94 | + |
| 95 | +**CLI** |
| 96 | + |
| 97 | +Use the [Scaleway command-line interface](/scaleway-cli/quickstart/) for easy resource management, scripting, and automation. |
| 98 | + |
| 99 | +**Terraform/IaC** |
| 100 | + |
| 101 | +Define your Serverless Containers services using tools like Terraform or OpenTofu via the [Scaleway Provider](/terraform/quickstart/) for a fully automated and declarative infrastructure. |
| 102 | + |
| 103 | +### Migration strategies |
| 104 | + |
| 105 | +**Progressive migration** |
| 106 | + |
| 107 | +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. |
| 108 | + |
| 109 | +**API migration** |
| 110 | + |
| 111 | +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. |
| 112 | + |
| 113 | +### Start small with Serverless Jobs |
| 114 | + |
| 115 | +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. |
| 116 | + |
| 117 | +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. |
| 118 | + |
| 119 | +Refer to the [Serverless Jobs quickstart guide](/serverless-jobs/quickstart/) to deploy your first job in a few minutes. |
0 commit comments