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: faq/serverless-containers.mdx
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,34 +10,34 @@ category: serverless
10
10
productIcon: ContainersProductIcon
11
11
---
12
12
13
-
## What is serverless computing and how does it differ from traditional cloud hosting?
13
+
## 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
-
## Why consider using Serverless Containers, Functions or Jobs for my projects?
17
+
## Why consider using Serverless Containers, Functions, or Jobs for my projects?
18
18
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 let you run large-scale, parallel batchprocessing tasks efficiently. This can lead to faster development cycles, reduced operational overhead, and cost savings.
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
## Can I run any application on Serverless Containers?
22
22
23
23
Yes. Because Serverless Containers supports any containerized application, you can choose the language, runtime, and framework that best suits your needs. As long as it can run in a container and respond to HTTP requests, Serverless Containers can host it.
24
24
25
25
## What are the cost benefits of using serverless services like Serverless Containers?
26
26
27
-
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.
27
+
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.
28
28
29
-
## Does updates of Serverless Containers can cause downtime?
29
+
## Can updates of Serverless Containers cause downtime?
30
30
31
-
No, when deploying a new version of your Serverless Container generates a **rolling update**. This means that a new version of the service is gradually
31
+
No, deploying a new version of your Serverless Container generates a **rolling update**. This means that a new version of the service is gradually
32
32
rolled out to your users without downtime. Here is how it works:
33
33
34
34
* When a new version of your container is deployed, the platform automatically starts routing traffic to the new version incrementally, while still serving requests from the old version until the new one is fully deployed.
35
-
* Once the new version is successfully running, we gradually shifts all traffic to it, ensuring zero downtime.
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 it.
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 it.
39
39
40
-
## Can I update Serverless Container ressources (vCPU and RAM) at any time?
40
+
## Can I upgrade Serverless Container resources (vCPU and RAM) at any time?
41
41
42
42
Yes, Serverless Containers ressources can be changed at any time without causing downtime, see previous question.
0 commit comments