Skip to content

Commit a920196

Browse files
chore(serverless): faq consistency (#5407)
1 parent 4ea0cc7 commit a920196

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

pages/serverless-containers/faq.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -125,13 +125,13 @@ This process ensures a seamless update experience, minimizing user disruption du
125125

126126
Yes. Many traditional applications can be containerized and deployed to Serverless Containers. This makes it easier to modernize legacy systems without a complete rewrite. By moving to a serverless platform, you gain automatic scaling, reduced operational overhead, and a simpler infrastructure management experience.
127127

128-
### How can I select the right resources (vCPU/RAM/ephemeral storage) for Serverless Containers ?
128+
### How can I select the right resources (vCPU/RAM/ephemeral storage) for Serverless Containers?
129129

130130
Insufficient vCPU, RAM or ephemeral storage can lead to containers going to error status. Make sure to provision enough resources for your container.
131131

132132
We recommend you set high values, [use metrics to monitor](/serverless-containers/how-to/monitor-container/) the resource usage of your container, then adjust the values accordingly.
133133

134-
### How can I reduce the cold-starts of Serverless Containers ?
134+
### How can I reduce the cold-starts of Serverless Containers?
135135

136136
* **Optimize the startup**: Cold-starts can be affected by loading a large number of dependencies and opening several resources at startup.
137137
Ensure that your code avoids heavy computations or long-running initialization at startup and optimize the number of loaded libraries.
@@ -173,7 +173,7 @@ There are several ways to deploy containers. Refer to the [dedicated documentati
173173

174174
Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/queues/concepts/#scaleway-queues) and [Topics and Events](/topics-and-events/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases-for-postgresql-and-mysql/) or [Serverless databases](/serverless-sql-databases/). [Serverless Jobs](/serverless-jobs/) can pull data from [Object Storage](/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.
175175

176-
### Where should I host my container images for deployment ?
176+
### Where should I host my container images for deployment?
177177

178178
<ContainerRegistryNote />
179179

@@ -198,19 +198,19 @@ Serverless Containers namespaces and Container Registry namespaces observe the f
198198
### How can I call my containers periodically?
199199

200200
Scaleway Serverless Containers natively support CRON triggers to call your containers periodically. This feature has many applications, such as scheduled data processing, maintenance tasks, monitoring, or reporting.
201-
201+
202202
Periodic CRON triggers also allow you to maintain your containers active during specific time slots to reduce cold start latency, without having to provision a minimum of 1 vCPU at all times.
203203

204204
Refer to the [dedicated documentation](/serverless-containers/how-to/add-trigger-to-a-container/) for more information on how to create CRON triggers for your containers.
205205

206206
To learn more about how CRONs work, refer to our [CRON schedule reference documentation](/serverless-containers/reference-content/cron-schedules/).
207207

208-
### How do Serverless Containers health checks work ?
208+
### How do Serverless Containers health checks work?
209209

210210
A Serverless Container is set to `ready` once the specified port is correctly bound to the container, and will start receiving traffic. If your application needs to perform some tasks before receiving traffic (e.g. connect to a database), it is important to run them before binding to the port (starting the webserver).
211211
For now, the `HEALTHCHECK` Docker directive has no impact on container readiness. In the future, the health check will be customizable for your applications.
212212

213-
### How do I know if my application is compatible with Serverless Containers ?
213+
### How do I know if my application is compatible with Serverless Containers?
214214

215215
Your application is compatible with Serverless Containers if it meets the following criteria:
216216

pages/serverless-functions/faq.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ You can create billing alerts to get notifications when your costs exceed a cert
129129

130130
## Resources and performance
131131

132-
### How to select the right resources (vCPU/RAM) for Serverless Functions ?
132+
### How to select the right resources (vCPU/RAM) for Serverless Functions?
133133

134134
Insufficient vCPU and RAM resources can lead to functions going to error status. Make sure to provision enough resources for your function.
135135

0 commit comments

Comments
 (0)