You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## What is serverless computing, and how does it differ from traditional cloud hosting?
14
14
15
-
Serverless computing is a cloud execution model where the cloud provider dynamically manages the allocation of compute resources. Unlike traditional hosting models, you don’t need to provision, scale, or maintain servers. Instead, you focus solely on writing and deploying your code, and the infrastructure scales automatically to meet demand.
15
+
Serverless computing is a cloud execution model where the cloud provider dynamically manages the allocation of compute resources. Unlike traditional hosting models, you do not need to provision, scale, or maintain servers. Instead, you focus solely on writing and deploying your code, and the infrastructure scales automatically to meet demand.
16
16
17
17
## Why consider using Serverless Containers, Functions, or Jobs for my projects?
18
18
19
19
These services allow you to build highly scalable, event-driven, and pay-as-you-go solutions. Serverless Containers and Functions help you create applications and microservices without worrying about server management, while Serverless Jobs lets you run large-scale, parallel batch-processing tasks efficiently. This can lead to faster development cycles, reduced operational overhead, and cost savings.
20
20
21
21
## What are the cost benefits of using serverless services like Serverless Containers and Serverless Functions?
22
22
23
-
With serverless, you only pay for the compute resources you actually use. There are no upfront provisioning costs or paying for idle capacity. When your application traffic is low, the cost scales down, and when traffic spikes, the platform automatically scales up, ensuring you never overpay for unused resources.
23
+
With serverless, you only pay for the computing resources you use. There are no upfront provisioning costs or paying for idle capacity. When your application traffic is low, the cost scales down, and when traffic spikes, the platform automatically scales up, ensuring you never overpay for unused resources.
24
24
25
25
## How does scaling work in these serverless services?
26
26
27
-
Scaling in Serverless Containers and Serverless Functions is handled automatically by the platform. When demand increases—more requests or events—the platform spins up additional instances to handle the load. When demand decreases, instances spin down. This ensures optimal performance without manual intervention.
27
+
Scaling in Serverless Containers and Serverless Functions is handled automatically by the platform. When demand increases - more requests or events - the platform spins up additional instances to handle the load. When demand decreases, instances spin down. This ensures optimal performance without manual intervention.
28
28
29
29
## Can updates of Serverless Function cause downtime?
30
30
@@ -35,15 +35,15 @@ rolled out to your users without downtime. Here is how it works:
35
35
* Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime.
36
36
* The old version is decommissioned once the new version is fully serving traffic.
37
37
38
-
This process ensures a seamless update experience, minimizing disruption to users during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to them.
38
+
This process ensures a seamless update experience, minimizing user disruption during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to them.
39
39
40
40
## Can I upgrade Serverless Function resources (vCPU and RAM) at any time?
41
41
42
42
Yes, Serverless Functions resources can be changed at any time without causing downtime, see the previous question for full details.
43
43
44
44
## How do I integrate my serverless solutions with other Scaleway services?
45
45
46
-
Integration is straightforward. Serverless Functions and Containers can be triggered by events from Queues, SQS and SNS and can easily communicate with services like Managed databases or Serverless databases. Serverless Jobs can pull data from Object Storage or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
46
+
Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/serverless/messaging/concepts/#queues) and [Topics and Events](/serverless/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless/sql-databases/). [Serverless Jobs](/serverless/jobs/) can pull data from [Object Storage](/storage/object), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
47
47
48
48
## How am I billed for Serverless Functions?
49
49
@@ -228,18 +228,18 @@ For some use cases, such as saving analysis results, exporting data etc., it can
228
228
229
229
### Databases
230
230
231
-
***Serverless Databases**: Go full serverless and take the complexity out of PostgreSQL database operations.
232
-
***Managed MySQL / PostgreSQL**: Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
233
-
***Managed Database for Redis®**: Fully managed Redis®* in seconds.
234
-
***Managed MongoDB®**: Get the best of MongoDB® and Scaleway in one database.
231
+
*[Serverless Databases](/serverless/sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations.
232
+
*[Managed MySQL / PostgreSQL](/managed-databases/postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
233
+
*[Managed Database for Redis®](/managed-databases/redis/): Fully managed Redis®* in seconds.
234
+
*[Managed MongoDB®](/managed-databases/mongodb/): Get the best of MongoDB® and Scaleway in one database.
235
235
236
236
### Storage
237
237
238
-
***Object Storage**: Multi-AZ resilient object storage service ensuring high availability for your data.
239
-
***Scaleway Glacier**: Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
238
+
*[Object Storage](/storage/object/): Multi-AZ resilient object storage service ensuring high availability for your data.
239
+
*[Scaleway Glacier](/storage/object/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
240
240
241
241
<Messagetype="tip">
242
-
Explore all Scaleway products on the console and select the right product for your use case.
242
+
Explore all Scaleway products in the console and select the right product for your use case.
243
243
244
244
Some products are not listed but for example, on specific use cases Secret Manager can help you to store informations that requires versioning.
## What is serverless computing, and how does it differ from traditional cloud hosting?
14
14
15
-
Serverless computing is a cloud execution model where the cloud provider dynamically manages the allocation of compute resources. Unlike traditional hosting models, you don’t need to provision, scale, or maintain servers. Instead, you focus solely on writing and deploying your code, and the infrastructure scales automatically to meet demand.
15
+
Serverless computing is a cloud execution model where the cloud provider dynamically manages the allocation of compute resources. Unlike traditional hosting models, you do not need to provision, scale, or maintain servers. Instead, you focus solely on writing and deploying your code, and the infrastructure scales automatically to meet demand.
16
16
17
17
## Why consider using Serverless Containers, Functions, or Jobs for my projects?
18
18
@@ -24,7 +24,7 @@ Serverless Jobs allows you to run large-scale batch processing and computational
24
24
25
25
## How do I integrate my serverless solutions with other Scaleway services?
26
26
27
-
Integration is straightforward. Serverless Functions and Containers can be triggered by events from Queues, SQS and SNS and can easily communicate with services like Managed databases or Serverless databases. Serverless Jobs can pull data from Object Storage or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
27
+
Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/serverless/messaging/concepts/#queues) and [Topics and Events](/serverless/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless/sql-databases/). [Serverless Jobs](/serverless/jobs/) can pull data from [Object Storage](/storage/object), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
28
28
29
29
## Can I update Serverless Jobs resources (vCPU and RAM) at any time?
30
30
@@ -151,18 +151,17 @@ In different use cases, such as saving analysis results and exporting data, it c
151
151
152
152
### Databases
153
153
154
-
***Serverless Databases**: Go full serverless and take the complexity out of PostgreSQL database operations.
155
-
***Managed MySQL / PostgreSQL**: Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
156
-
***Managed Database for Redis®**: Fully managed Redis®* in seconds.
157
-
***Managed MongoDB®**: Get the best of MongoDB® and Scaleway in one database.
154
+
*[Serverless Databases](/serverless/sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations.
155
+
*[Managed MySQL / PostgreSQL](/managed-databases/postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
156
+
*[Managed MongoDB®](/managed-databases/mongodb/): Get the best of MongoDB® and Scaleway in one database.
158
157
159
158
### Storage
160
159
161
-
***Object Storage**: Multi-AZ resilient object storage service ensuring high availability for your data.
162
-
***Scaleway Glacier**: Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
160
+
*[Object Storage](/storage/object/): Multi-AZ resilient object storage service ensuring high availability for your data.
161
+
*[Scaleway Glacier](/storage/object/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
163
162
164
163
<Messagetype="tip">
165
-
Explore all Scaleway products on the console and select the right product for your use case.
164
+
Explore all Scaleway products in the console and select the right product for your use case.
166
165
167
166
Some products are not listed but for example, on specific use cases Secret Manager can help you to store informations that requires versioning.
Copy file name to clipboardExpand all lines: serverless/containers/concepts.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ A container image is a file that includes all the requirements and instructions
39
39
40
40
## Container Registry
41
41
42
-
Container Registry is the place where your images are stored before being deployed, we recommend using Scaleway Container Registry for optimal integration. [Migration guide](/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry/).
42
+
Container Registry is the place where your images are stored before being deployed. We recommend using Scaleway Container Registry for optimal integration. See the [migration guide](/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry/) for full details.
43
43
44
44
## CRON trigger
45
45
@@ -198,7 +198,7 @@ Here is how it works:
198
198
* Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime.
199
199
* The old version is decommissioned once the new version is fully serving traffic.
200
200
201
-
This process ensures a seamless update experience, minimizing disruption to users during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to it
201
+
This process ensures a seamless update experience, minimizing user disruption during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to it
0 commit comments