Skip to content

Commit 8616c11

Browse files
thomas-tacquetthomas-tacquet
committed
doc(serverless): long running tasks change
1 parent cbb5f2b commit 8616c11

File tree

1 file changed

+18
-18
lines changed

1 file changed

+18
-18
lines changed

‎macros/serverless/difference-jobs-functions-containers.mdx‎

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -12,23 +12,23 @@ macro: difference-jobs-functions-containers
1212

1313
### Comparison table
1414

15-
| **Criteria** | **Serverless Functions** | **Serverless Containers** | **Serverless Jobs** |
16-
|------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------|
17-
| **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 |
18-
| **Scaling** | Automatically scales based on incoming events | Automatically scales based on incoming events | Manually specified number of job executions |
19-
| **Maximum execution time** | Up to one hour per request | Up to one hour per request | 24 hours |
20-
| **Concurrency** | Single request per instance | Configurable concurrency per instance | Not applicable |
21-
| **Pricing model** | Pay based on execution time and invocations | Pay based on vCPU and memory usage | Pay based on vCPU and memory usage |
22-
| **Triggers** | HTTP requests, scheduled (CRONs), messaging events (NATS, SQS, SNS) | HTTP requests, scheduled (CRONs), messaging events (NATS, SQS, SNS) | Manual invocation or scheduled |
23-
| **Language support** | Node, PHP, Python, Go, Rust | Any language/runtime within a container | Any language/runtime within a container |
24-
| **Infrastructure management** | Fully managed, handles provisioning and scaling automatically | Fully managed, handles provisioning and scaling automatically | Fully managed, abstracts away infrastructure management |
25-
| **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) |
26-
| **Supports custom containers** | No, deploy code in supported languages only | Yes, deploy any containerized application | Yes, deploy any containerized application |
27-
| **Long-running processes** | Not suitable for long running tasks | Not suitable for long running tasks | Ideal for long running processes |
28-
| **Networking** | Supports VPC integration | Supports VPC integration | No VPC support at the moment |
29-
| **Secret manager integration** | Only via local secrets | Only via local secrets | Yes |
30-
| **Customizable ephemeral storage** | Yes | Yes | Yes |
31-
| **Scaling from and to zero** | Yes | Yes | Not applicable |
15+
| **Criteria** | **Serverless Functions** | **Serverless Containers** | **Serverless Jobs** |
16+
|----------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------|
17+
| **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 |
18+
| **Scaling** | Automatically scales based on incoming events | Automatically scales based on incoming events | Manually specified number of job executions |
19+
| **Maximum execution time** | Up to one hour per request | Up to one hour per request | 24 hours |
20+
| **Concurrency** | Single request per instance | Configurable concurrency per instance | Not applicable |
21+
| **Pricing model** | Pay based on execution time and invocations | Pay based on vCPU and memory usage | Pay based on vCPU and memory usage |
22+
| **Triggers** | HTTP requests, scheduled (CRONs), messaging events (NATS, SQS, SNS) | HTTP requests, scheduled (CRONs), messaging events (NATS, SQS, SNS) | Manual invocation or scheduled |
23+
| **Language support** | Node, PHP, Python, Go, Rust | Any language/runtime within a container | Any language/runtime within a container |
24+
| **Infrastructure management** | Fully managed, handles provisioning and scaling automatically | Fully managed, handles provisioning and scaling automatically | Fully managed, abstracts away infrastructure management |
25+
| **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) |
26+
| **Supports custom containers** | No, deploy code in supported languages only | Yes, deploy any containerized application | Yes, deploy any containerized application |
27+
| **Long background tasks** | Not suitable for long running tasks | Not suitable for long running tasks | Ideal for long running processes |
28+
| **Networking** | Supports VPC integration | Supports VPC integration | No VPC support at the moment |
29+
| **Secret manager integration** | Only via local secrets | Only via local secrets | Yes |
30+
| **Customizable ephemeral storage** | Yes | Yes | Yes |
31+
| **Scaling from and to zero** | Yes | Yes | Not applicable |
3232

3333
## Details
3434

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

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

0 commit comments

Comments
 (0)