Skip to content

doc(serverless): long running tasks change #5526

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.

Sign up for GitHub

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 2 commits into from
Sep 17, 2025
Merged

doc(serverless): long running tasks change #5526

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8616c11
doc(serverless): long running tasks change
thomas-tacquet Sep 17, 2025
315e996
wording
thomas-tacquet Sep 17, 2025
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
36 changes: 18 additions & 18 deletions macros/serverless/difference-jobs-functions-containers.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,23 +12,23 @@ macro: difference-jobs-functions-containers

### Comparison table

| **Criteria** | **Serverless Functions** | **Serverless Containers** | **Serverless Jobs** |
|------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------|
| **Use case** | Event-driven functions responding to events or HTTP requests | Stateless HTTP containers handling web services or APIs | Processing tasks that run to completion |
| **Scaling** | Automatically scales based on incoming events | Automatically scales based on incoming events | Manually specified number of job executions |
| **Maximum execution time** | Up to one hour per request | Up to one hour per request | 24 hours |
| **Concurrency** | Single request per instance | Configurable concurrency per instance | Not applicable |
| **Pricing model** | Pay based on execution time and invocations | Pay based on vCPU and memory usage | Pay based on vCPU and memory usage |
| **Triggers** | HTTP requests, scheduled (CRONs), messaging events (NATS, SQS, SNS) | HTTP requests, scheduled (CRONs), messaging events (NATS, SQS, SNS) | Manual invocation or scheduled |
| **Language support** | Node, PHP, Python, Go, Rust | Any language/runtime within a container | Any language/runtime within a container |
| **Infrastructure management** | Fully managed, handles provisioning and scaling automatically | Fully managed, handles provisioning and scaling automatically | Fully managed, abstracts away infrastructure management |
| **Cold-starts** | There may be startup latency on new instances | There may be startup latency on new instances | Not applicable (jobs starts when scheduled or invoked) |
| **Supports custom containers** | No, deploy code in supported languages only | Yes, deploy any containerized application | Yes, deploy any containerized application |
| **Long-running processes** | Not suitable for long running tasks | Not suitable for long running tasks | Ideal for long running processes |
| **Networking** | Supports VPC integration | Supports VPC integration | No VPC support at the moment |
| **Secret manager integration** | Only via local secrets | Only via local secrets | Yes |
| **Customizable ephemeral storage** | Yes | Yes | Yes |
| **Scaling from and to zero** | Yes | Yes | Not applicable |
| **Criteria** | **Serverless Functions** | **Serverless Containers** | **Serverless Jobs** |
|----------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------|
| **Use case** | Event-driven functions responding to events or HTTP requests | Stateless HTTP containers handling web services or APIs | Processing tasks that run to completion |
| **Scaling** | Automatically scales based on incoming events | Automatically scales based on incoming events | Manually specified number of job executions |
| **Maximum execution time** | Up to one hour per request | Up to one hour per request | 24 hours |
| **Concurrency** | Single request per instance | Configurable concurrency per instance | Not applicable |
| **Pricing model** | Pay based on execution time and invocations | Pay based on vCPU and memory usage | Pay based on vCPU and memory usage |
| **Triggers** | HTTP requests, scheduled (CRONs), messaging events (NATS, SQS, SNS) | HTTP requests, scheduled (CRONs), messaging events (NATS, SQS, SNS) | Manual invocation or scheduled |
| **Language support** | Node, PHP, Python, Go, Rust | Any language/runtime within a container | Any language/runtime within a container |
| **Infrastructure management** | Fully managed, handles provisioning and scaling automatically | Fully managed, handles provisioning and scaling automatically | Fully managed, abstracts away infrastructure management |
| **Cold-starts** | There may be startup latency on new instances | There may be startup latency on new instances | Not applicable (jobs starts when scheduled or invoked) |
| **Supports custom containers** | No, deploy code in supported languages only | Yes, deploy any containerized application | Yes, deploy any containerized application |
| **Long background tasks** | Not optimal for long running tasks | Not optimal for long running tasks | Ideal for long running background processes |
| **Networking** | Supports VPC integration | Supports VPC integration | No VPC support at the moment |
| **Secret manager integration** | Only via local secrets | Only via local secrets | Yes |
| **Customizable ephemeral storage** | Yes | Yes | Yes |
| **Scaling from and to zero** | Yes | Yes | Not applicable |

## Details

Expand Down Expand Up @@ -72,4 +72,4 @@ Choose Scaleway [Serverless Containers](/serverless-containers/quickstart/):

<Message type="note">
To run as a Serverless Container, your application must be containerized, giving you a lot of flexibility to configure your runtime environments.
</Message>
</Message>