-
Notifications
You must be signed in to change notification settings - Fork 248
feat(containers): product handbook doc #5018
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
6d33c91
draft: feat(containers): product doc
thomas-tacquet 8fec8fa
Merge branch 'main' into serverless-containers-product-doc
thomas-tacquet a28e0b0
add more content
thomas-tacquet d0c918b
mv
thomas-tacquet f911e36
description
thomas-tacquet 9c2aed1
review
thomas-tacquet f94b150
Apply suggestions from code review
thomas-tacquet e36fc35
Update pages/serverless-containers/reference-content/serverless-handb…
thomas-tacquet 3b2b488
small workloads sentence
thomas-tacquet ea72744
rename page to serverless overview
thomas-tacquet b827121
add item in menu
thomas-tacquet f01bd65
Update pages/serverless-containers/reference-content/serverless-overv…
thomas-tacquet 2ca8a78
add more links
thomas-tacquet 6eacc5d
docs(srv): update
SamyOubouaziz 69bcaae
docs(srv): update
SamyOubouaziz c173255
Merge branch 'main' into serverless-containers-product-doc
thomas-tacquet File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
91 changes: 91 additions & 0 deletions
91
...s/serverless-containers/reference-content/understanding-serverless-benefits.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,91 @@ | ||
--- | ||
meta: | ||
title: Understanding Serverless benefits | ||
description: | ||
content: | ||
h1: Understanding Serverless benefits | ||
paragraph: | ||
thomas-tacquet marked this conversation as resolved.
Show resolved
Hide resolved
|
||
tags: containers serverless | ||
dates: | ||
validation: 2025-05-23 | ||
posted: 2025-05-23 | ||
categories: | ||
- serverless | ||
- containers | ||
--- | ||
|
||
# What is Serverless Compute? | ||
|
||
Serverless computing is a cloud computing model where the cloud providers manages the infrastructure and dynamically alocates computing resources as needed. | ||
|
||
This means that you don't have to provision machines, manage a cluster or pay for servers. Your application code is executed on demand and you only pay for the compute time consumed by your software. | ||
|
||
This approach enables greater scalability, flexibility and cost-effectiveness. | ||
|
||
Key features: | ||
* **Automatic scaling:** your application can scale up or down automatically based on demand | ||
* **No server management:** you don't need to provision, maintain or manage servers | ||
* **Pay as ou go:** you only pay for the compute time you consume, making it cost effective | ||
|
||
Serverless is not limited to Serverless Function which is perfect to deploy small chunks of code, it can also directly deploy containers on Serverless Containers and Serverless Jobs. | ||
thomas-tacquet marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
# Why Serverless? | ||
|
||
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. | ||
* **Scalability:** Automatically scale your applications to handle varying loads without manual intervention. It's perfect for seasonal traffic and viral apps. | ||
* **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. | ||
|
||
|
||
# How to control costs of Serverless? | ||
|
||
Serverless is inherently cost-transparent, tips to otpimize costs: | ||
* Use efficient code and set timeouts | ||
* Monitor usage with built-in observability | ||
* Define a max-scale setting | ||
|
||
Remember: Serverless eliminates upfront capital expenses and reduces operational costs giving you predictable, granular billing. | ||
|
||
# Ready to go Serverless? | ||
|
||
By adopting Serverless, you are choosing agility, innovation, and cost savings. | ||
Whether you are a startup scaling rapidly or an enterprise modernizing legacy systems, Serverless lets you focus on what matters: delivering value to your users. | ||
|
||
You can fully deploy your API on Serverless or use it to emporer and add automation to your infrastructure. | ||
Serverless is excellent at handling traffic spikes, useful to offload regular servers on special events. | ||
|
||
# Is my applicaiton a good fit for Serverless? | ||
Most applications can benefit from Serverless! Here's when it shines: | ||
|
||
* Event driven workloads: file processing, real time notification, IoT data streams. | ||
* Microservies and APIs: Stateless, short-lived tasks (e.g., user authentication, payment processing, etc...) | ||
* Sporadic traffic: Aps with variable usage (e.g., marketing campaigns, ticketing system). | ||
* Rapid prototyping: Test ideas quickly without upfront infrastructure investment | ||
|
||
# How secure are Serverless resources? | ||
|
||
**Isolation:** Each container runs in a secure, isolated environment | ||
**IAM integration:** Fine-grained access control via IAM, inject directly required redentials to Serverless ressources. | ||
|
||
# How do I debug and monitor applications in a Serverless environment? | ||
|
||
Scaleway provides full observability: | ||
|
||
* **Logs and metrics:** Centralized logging and real-time metrics via Cockpit | ||
* **Local debugging:** Test containers locally using the Serverless CLI and emulator | ||
* **Error Reporting:** Automatic alerts for failed invocations or resource bottlenecks via Cockpit | ||
|
||
# Will Serverless lock me into the ecosystem? | ||
No. Scaleway Serverless is designed to minimize vendor lock-in. | ||
We believe in empowering your freedom to choose, adapt, and evolve. Here is how we ensure flexibility: | ||
|
||
## Container portability | ||
- **Docker compatibility**: Your container images (built with Docker, Helm, or other tools) are portable. You can redeploy them elsewhere—on-premises, on other clouds, or in hybrid environments. | ||
- **No proprietary formats**: We don't modify your containers. What you build works anywhere. | ||
|
||
## No proprietary lock-in | ||
- **No forced dependencies** | ||
- **Open APIs**: Manage Serverless Containers via REST APIs, Terraform, CLI, etc... no proprietary control required. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.