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
Copy file name to clipboardExpand all lines: pages/serverless-containers/faq.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,13 +125,13 @@ This process ensures a seamless update experience, minimizing user disruption du
125
125
126
126
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.
127
127
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?
129
129
130
130
Insufficient vCPU, RAM or ephemeral storage can lead to containers going to error status. Make sure to provision enough resources for your container.
131
131
132
132
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.
133
133
134
-
### How can I reduce the cold-starts of Serverless Containers?
134
+
### How can I reduce the cold-starts of Serverless Containers?
135
135
136
136
***Optimize the startup**: Cold-starts can be affected by loading a large number of dependencies and opening several resources at startup.
137
137
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
173
173
174
174
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.
175
175
176
-
### Where should I host my container images for deployment?
176
+
### Where should I host my container images for deployment?
177
177
178
178
<ContainerRegistryNote />
179
179
@@ -198,19 +198,19 @@ Serverless Containers namespaces and Container Registry namespaces observe the f
198
198
### How can I call my containers periodically?
199
199
200
200
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
+
202
202
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.
203
203
204
204
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.
205
205
206
206
To learn more about how CRONs work, refer to our [CRON schedule reference documentation](/serverless-containers/reference-content/cron-schedules/).
207
207
208
-
### How do Serverless Containers health checks work?
208
+
### How do Serverless Containers health checks work?
209
209
210
210
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).
211
211
For now, the `HEALTHCHECK` Docker directive has no impact on container readiness. In the future, the health check will be customizable for your applications.
212
212
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?
214
214
215
215
Your application is compatible with Serverless Containers if it meets the following criteria:
0 commit comments