-
Notifications
You must be signed in to change notification settings - Fork 244
feat(serverless): add overview to jobs and functions #5141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
||
Serverless computing is a cloud computing model where the cloud providers manage the infrastructure and dynamically allocate computing resources as needed. | ||
|
||
This means that there is no need to provision machines, manage a cluster, or pay for servers. Your application code is executed on demand, and you only pay for the computing time consumed by your software. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This means that there is no need to provision machines, manage a cluster, or pay for servers. Your application code is executed on demand, and you only pay for the computing time consumed by your software. | |
This means that there is no need for users to provision machines, manage a cluster, or pay for servers. Your application code is executed on demand, and you only pay for the computing time consumed by your software. |
* **No server management:** No need to provision, maintain, or manage servers | ||
* **Pay as you go:** Only pay for the computing time you consume, making it cost-effective | ||
|
||
Serverless is not limited to Serverless Functions which is perfect to deploy small chunks of code, it can also directly deploy containers on Serverless Containers and Serverless Jobs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Serverless is not limited to Serverless Functions which is perfect to deploy small chunks of code, it can also directly deploy containers on Serverless Containers and Serverless Jobs. | |
The Scaleway Serverless ecosystem is not limited to Serverless Functions, which is perfect to deploy small chunks of code. You can also directly deploy containers on Serverless Containers and Serverless Jobs. |
|
||
Serverless offers numerous advantages that can significantly enhance your development and operational efficiency: | ||
|
||
* **Cost savings:** You only pay for the compute time your code uses, which can lead to significant cost reductions. No idle resources |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* **Cost savings:** You only pay for the compute time your code uses, which can lead to significant cost reductions. No idle resources | |
* **Cost savings:** You only pay for the compute time your code uses, which can lead to significant cost reductions. No idle resources are left running and incurring unnecessary costs |
* **Faster time to market:** Focus on writing code rather than managing infrastructure, accelerating your development cycles | ||
* **Reduced operational overhead:** Let the cloud provider handle server maintenance, updates, and scaling, freeing up your team to focus on innovation | ||
* **Eco-friendly:** Optimized resource usage reduces wasted energy | ||
* **Focus on apps:** you can put all your energy into the application value instead of managing infrastructures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* **Focus on apps:** you can put all your energy into the application value instead of managing infrastructures | |
* **Focus on apps:** You can put all your energy into building application value instead of managing infrastructure |
* **Eco-friendly:** Optimized resource usage reduces wasted energy | ||
* **Focus on apps:** you can put all your energy into the application value instead of managing infrastructures | ||
|
||
## How to control the costs of Serverless? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## How to control the costs of Serverless? | |
## How to control Serverless costs |
### Learn Serverless basics | ||
|
||
* **Minimal learning curve:** Teams only need to understand event-driven architecture, container basics, and Scaleway’s serverless console/CLI | ||
* **Training resources:** Free tutorials, examples, and free-tier to experiment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* **Training resources:** Free tutorials, examples, and free-tier to experiment | |
* **Training resources:** Free tutorials, examples, and free tier for experiments and testing |
### Auto-Scaling for traffic spikes | ||
|
||
* **Zero manual intervention:** Automatically scale from zero to millions of requests during flash sales, marketing campaigns, or viral events | ||
* **Example:** An e-commerce app handles black friday traffic seamlessly without provisioning extra resources |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* **Example:** An e-commerce app handles black friday traffic seamlessly without provisioning extra resources | |
* **Example:** An e-commerce app handles Black Friday traffic seamlessly without provisioning extra resources |
### Enterprise-Ready as you scale | ||
|
||
* **SLAs and security:** Check our [SLA page](https://www.scaleway.com/en/terms/sla/) | ||
* **Hybrid flexibility:** Seamlessly integrate with other Scaleway services (e.g., databases, messaging, AI/ML) to support complex workflows |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* **Hybrid flexibility:** Seamlessly integrate with other Scaleway services (e.g., databases, messaging, AI/ML) to support complex workflows | |
* **Hybrid flexibility:** Seamlessly integrate with other Scaleway services (e.g., Managed Databases, Queues, Topics and Events, and Managed Inference) to support complex workflows |
@@ -0,0 +1,154 @@ | |||
--- | |||
meta: | |||
title: Serverless overview |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would consider renaming this "Serverless Benefits" / "Advantages of Serverless" or similar. To me, an Overview would be a bit more about how the product actually works, whereas this document is more about what the user has to gain.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is to be identical with https://www.scaleway.com/en/docs/serverless-containers/reference-content/serverless-overview/
Global idea is to help people discovering and exploring the product via our documentation. It's important to be neutral without speaking about benefits and advantages as we do not have similar pages, there are concepts but it's closer to a dictionary to me
@@ -0,0 +1,158 @@ | |||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apply all same comments/suggestions as above
Add https://github.com/scaleway/docs-content/pull/5018/files to Jobs and Functions