Skip to content

Commit e217872

Browse files
apply comments
1 parent ea87c6a commit e217872

File tree

4 files changed

+23
-24
lines changed

4 files changed

+23
-24
lines changed

faq/serverless-functions.mdx

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -12,19 +12,19 @@ productIcon: FunctionsProductIcon
1212

1313
## What is serverless computing, and how does it differ from traditional cloud hosting?
1414

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.
1616

1717
## Why consider using Serverless Containers, Functions, or Jobs for my projects?
1818

1919
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.
2020

2121
## What are the cost benefits of using serverless services like Serverless Containers and Serverless Functions?
2222

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.
2424

2525
## How does scaling work in these serverless services?
2626

27-
Scaling in Serverless Containers and Serverless Functions is handled automatically by the platform. When demand increasesmore requests or eventsthe 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.
2828

2929
## Can updates of Serverless Function cause downtime?
3030

@@ -35,15 +35,15 @@ rolled out to your users without downtime. Here is how it works:
3535
* Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime.
3636
* The old version is decommissioned once the new version is fully serving traffic.
3737

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.
3939

4040
## Can I upgrade Serverless Function resources (vCPU and RAM) at any time?
4141

4242
Yes, Serverless Functions resources can be changed at any time without causing downtime, see the previous question for full details.
4343

4444
## How do I integrate my serverless solutions with other Scaleway services?
4545

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.
4747

4848
## How am I billed for Serverless Functions?
4949

@@ -228,18 +228,18 @@ For some use cases, such as saving analysis results, exporting data etc., it can
228228

229229
### Databases
230230

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.
235235

236236
### Storage
237237

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.
240240

241241
<Message type="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.
243243

244244
Some products are not listed but for example, on specific use cases Secret Manager can help you to store informations that requires versioning.
245245
</Message>

faq/serverless-jobs.mdx

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ productIcon: ServerlessJobsProductIcon
1212

1313
## What is serverless computing, and how does it differ from traditional cloud hosting?
1414

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.
1616

1717
## Why consider using Serverless Containers, Functions, or Jobs for my projects?
1818

@@ -24,7 +24,7 @@ Serverless Jobs allows you to run large-scale batch processing and computational
2424

2525
## How do I integrate my serverless solutions with other Scaleway services?
2626

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.
2828

2929
## Can I update Serverless Jobs resources (vCPU and RAM) at any time?
3030

@@ -151,18 +151,17 @@ In different use cases, such as saving analysis results and exporting data, it c
151151

152152
### Databases
153153

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.
158157

159158
### Storage
160159

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.
163162

164163
<Message type="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.
166165

167166
Some products are not listed but for example, on specific use cases Secret Manager can help you to store informations that requires versioning.
168167
</Message>

serverless/containers/concepts.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ A container image is a file that includes all the requirements and instructions
3939

4040
## Container Registry
4141

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.
4343

4444
## CRON trigger
4545

@@ -198,7 +198,7 @@ Here is how it works:
198198
* Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime.
199199
* The old version is decommissioned once the new version is fully serving traffic.
200200

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
202202

203203
## Stateless application
204204

serverless/functions/concepts.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ Environment variables are key/value pairs injected in your container. They are u
5151

5252
## GB-s
5353

54-
Unit used to measure the resource consumption of a function. It reflects the amount of memory consumed over time.
54+
Unit used to measure the resource consumption of a Serverless Function. It reflects the amount of memory consumed over time.
5555

5656
## JWT Token
5757

0 commit comments

Comments
 (0)