Skip to content

feat(containers): product handbook doc #5018

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 16 commits into from
Jun 11, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions menu/navigation.json
Original file line number Diff line number Diff line change
Expand Up @@ -4405,6 +4405,10 @@
},
{
"items": [
{
"label": "Serverless overview",
"slug": "serverless-overview"
},
{
"label": "Containers limitations",
"slug": "containers-limitations"
Expand Down
4 changes: 3 additions & 1 deletion pages/serverless-containers/concepts.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -173,7 +173,7 @@ The container can then process the message and perform any required actions, suc

The port of a containerized application refers to the network port that the application inside the container listens on for incoming requests.

Refer to the [dedicated documentation](/serverless-containers/reference-content/port-parameter-variable/) for more information and examples on the **Port** parameter of Serverless Containers.
Refer to the [dedicated documentation](/serverless-containers/reference-content/port-parameter-variable/) for more information and examples on the **Port** parameter of Serverless Containers.

## Privacy policy

Expand Down Expand Up @@ -229,6 +229,8 @@ One of the advantages of Serverless Containers is that when your container is no

Secrets are an extra-secure type of environment variable. They are environment variables that are injected into your container and stored securely, but not displayed in the console after initial validation.

For more details about Serverless advantages, [read Serverless Overview](/serverless-containers/reference-content/serverless-overview/).

## Serverless

Serverless allows you to deploy your Functions (FaaS) and Containerized Applications (CaaS) in a managed infrastructure. Scaleway ensures the deployment, availability, and scalability of all your projects.
Expand Down
6 changes: 5 additions & 1 deletion pages/serverless-containers/quickstart.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,10 @@ categories:

Scaleway Serverless Containers provides you with containerized stateless web applications deployed in the cloud. They are designed for short-lived, event-driven tasks.

<Message>
For more details about Serverless advantages, [read Serverless Overview](/serverless-containers/reference-content/serverless-overview/).
</Message>

Containers rely on the HTTP protocol, and must therefore include a web server to work properly. Refer to the [differences between Containers, Jobs, and Functions](/serverless-containers/reference-content/difference-jobs-functions-containers/) for more information on Scaleway's different Serverless products.

This page explains how to deploy a basic NGINX image in a Serverless Container using the Scaleway console.
Expand Down Expand Up @@ -118,4 +122,4 @@ If you have no existing Serverless Containers resources in your current Project,

For advanced usage, such as larger projects with dependencies, automation, multiple containers, and more, there are [several ways to deploy containers](/serverless-containers/reference-content/deploy-container/).

Check out our [GitHub repository](https://github.com/scaleway/serverless-examples) for real-world examples.
Check out our [GitHub repository](https://github.com/scaleway/serverless-examples) for real-world examples.
Original file line number Diff line number Diff line change
@@ -0,0 +1,158 @@
---
meta:
title: Serverless overview
description: Understand the concepts and benefits of Serverless computing on Scaleway.
content:
h1: Serverless overview
paragraph: Understand the concepts and benefits of Serverless computing on Scaleway.
tags: containers serverless
dates:
validation: 2025-05-23
posted: 2025-05-23
categories:
- serverless
- containers
---

## What is serverless compute?

Serverless computing is a cloud computing model where the cloud providers manage the infrastructure and dynamically allocate computing resources as needed.

This means that there is no need to provision machines, manage a cluster, or pay for servers. Your application code is executed on demand, and you only pay for the computing time consumed by your software.

This approach enables greater scalability, flexibility, and cost-effectiveness.

Key features:
* **Automatic scaling:** Your application can scale up or down automatically based on demand
* **No server management:** No need to provision, maintain, or manage servers
* **Pay as you go:** Only pay for the computing time you consume, making it cost-effective

Serverless is not limited to Serverless Functions which is perfect to deploy small chunks of code, it can also directly deploy containers on Serverless Containers and Serverless Jobs.
Refer to the [differences between Functions, Jobs, and Containers](/serverless-containers/reference-content/difference-jobs-functions-containers/) for more information on Scaleway's different Serverless products.

## Why Serverless?

Serverless offers numerous advantages that can significantly enhance your development and operational efficiency:

* **Cost savings:** You only pay for the compute time your code uses, which can lead to significant cost reductions. No idle resources
* **Scalability:** Automatically scale your applications to handle varying loads without manual intervention. It is perfect for seasonal traffic and viral apps
* **Faster time to market:** Focus on writing code rather than managing infrastructure, accelerating your development cycles
* **Reduced operational overhead:** Let the cloud provider handle server maintenance, updates, and scaling, freeing up your team to focus on innovation
* **Eco-friendly:** Optimized resource usage reduces wasted energy
* **Focus on apps:** you can put all your energy into the application value instead of managing infrastructures

## How to control the costs of Serverless?

Serverless is inherently cost-transparent. Here are some tips to optimize costs:
* **Cost estimator:** When deploying Serverless resources via Scaleway Console, you can try different parameters to evaluate costs
* **Best practices** Use efficient code with optimized libraries, ensuring a small resource footprint
* **Monitoring** Monitor usage with built-in observability and use Cost Manager: [How to use cost manager documentation](/billing/how-to/use-the-cost-manager/)
* **Parameters** Define a max-scale setting according to traffic spikes

Remember: Serverless eliminates upfront capital expenses and reduces operational costs giving you predictable, granular billing.

## Ready to go Serverless?

By adopting Serverless, you are choosing agility, innovation, and cost savings.
Whether you are a startup scaling rapidly or an enterprise modernizing legacy systems, Serverless lets you focus on what matters: delivering value to your users.

You can fully deploy your API on Serverless or use it to empower and add automation to your infrastructure.
Serverless is excellent at handling traffic spikes, which is useful for offloading regular servers during special events.

## Is my application a good fit for serverless?

Most applications can benefit from serverless. Check some use cases:

* **Event-driven workloads:** file processing, real-time notification, IoT data streams
* **Microservices and APIs:** Stateless, short-lived tasks (e.g., user authentication, payment processing, etc.)
* **Sporadic traffic:** Apps with variable usage (e.g., marketing campaigns, ticketing system).
* **Rapid prototyping:** Test ideas quickly without upfront infrastructure investment

## How secure are Serverless resources?

Scaleway prioritizes strong security and isolation for Serverless products.

* **Secured isolation layers:** Each container runs in a secure, isolated environment. Our systems provide a VM-like security while maintaining container-like performance

## How do I debug and monitor applications in a Serverless environment?

Scaleway provides full observability:

* **Logs and metrics:** Centralized logging and real-time metrics via Cockpit
* **Local debugging:** Test containers locally using the Serverless CLI and emulator
* **Error Reporting:** Automatic alerts for failed invocations or resource bottlenecks via Cockpit. See [how to configure alerts for Serverless Containers](/serverless-containers/how-to/configure-alerts-containers/)

As our Serverless environment does not encourage vendor-locking, you can easily debug your container locally.

## Will Serverless lock me into the ecosystem?

No. Scaleway Serverless is designed to minimize vendor lock-in.
We believe in empowering your freedom to choose, adapt, and evolve. Here is how we ensure flexibility:

### Container portability
- **Docker compatibility**: Your container images (built with Docker, Helm, or other tools) are portable. You can redeploy them elsewhere—on-premises, on other clouds, or in hybrid environments.
- **No proprietary formats**: We do not modify your containers. What you build works anywhere.

### No proprietary lock-in
- **No forced dependencies**: Some providers require customers to import specific libraries to work properly. We do not.
- **Open APIs**: Manage Serverless Containers via REST APIs, Terraform, CLI, and more with no proprietary control required.

## How to migrate to a Serverless ecosystem?

Serverless products at Scaleway allow you to gradually migrate to Serverless, offering different strategies:

### Start small

* **Small workloads:** Migrate non-critical workloads first, like parts of APIs, automation, and scheduled tasks
* **Proof of concept:** Use our tutorial and check our [scaleway/serverless-examples repository](https://github.com/scaleway/serverless-examples) for inspiration

### Hybrid architecture

* **Coexistence:** Run serverless endpoints alongside VMs, clusters, and traditional apps

### Incremental refactoring

* **Break monoliths:** Convert microservices or stateless components to Serverless first

## What specific knowledge is required to deploy Serverless projects?

Serverless is designed to eliminate infrastructure complexity, so teams can focus on innovation:

### No infrastructure expertise needed

* **Managed services:** Scaleway handles networking, scaling, patching, and availability
* **Simplified operations:** No need for DevOps engineers to manage clusters or servers

### Developer-centric workflow

* **Familiar tools:** Use Git, Docker, CI/CD pipelines, and IDEs you already know
* **Language flexibility:** Support for Python, Node.js, Rust, Go, PHP, and custom runtimes via Serverless Containers

### Learn Serverless basics

* **Minimal learning curve:** Teams only need to understand event-driven architecture, container basics, and Scaleway’s serverless console/CLI
* **Training resources:** Free tutorials, examples, and free-tier to experiment

## Is Serverless a good choice for a growing business?

Absolutely. Serverless is ideal for startups and scaling businesses due to its cost efficiency, elasticity, and operational simplicity:

### Auto-Scaling for traffic spikes

* **Zero manual intervention:** Automatically scale from zero to millions of requests during flash sales, marketing campaigns, or viral events
* **Example:** An e-commerce app handles black friday traffic seamlessly without provisioning extra resources

### Pay-as-you-go cost model

* **No idle costs:* Growing businesses avoid overspending on underutilized infrastructure
* **Predictable budgeting:** Use cost estimator to forecast costs based on expected usage

### Focus on core innovation

* **Reduce operational overhead:** Teams avoid spending time on server management, freeing resources for product development
* **Faster iteration:** Deploy updates in minutes without downtime

### Enterprise-Ready as you scale

* **SLAs and security:** Check our [SLA page](https://www.scaleway.com/en/terms/sla/)
* **Hybrid flexibility:** Seamlessly integrate with other Scaleway services (e.g., databases, messaging, AI/ML) to support complex workflows