feat(serverless): add overview to jobs and functions #5141
There are no files selected for viewing
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
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
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
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
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,154 @@ | ||||||
| --- | ||||||
| meta: | ||||||
| title: Serverless overview | ||||||
| description: Understand the concepts and benefits of Serverless computing on Scaleway. | ||||||
| content: | ||||||
| h1: Serverless overview | ||||||
| paragraph: Understand the concepts and benefits of Serverless computing on Scaleway. | ||||||
| tags: functions serverless | ||||||
| dates: | ||||||
| validation: 2025-06-18 | ||||||
| posted: 2025-06-18 | ||||||
| categories: | ||||||
| - serverless | ||||||
| - functions | ||||||
| --- | ||||||
|
|
||||||
| ## What is serverless compute? | ||||||
|
|
||||||
| 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.
Suggested change
|
||||||
|
|
||||||
| 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:** 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.
Suggested change
|
||||||
| Refer to the [differences between Functions, Jobs, and Containers](/serverless-functions/reference-content/difference-jobs-functions-containers/) for more information on Scaleway's different Serverless products. | ||||||
|
|
||||||
| ## 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 | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
| * **Scalability:** Automatically scale your applications to handle varying loads without manual intervention. It is 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 | ||||||
| * **Focus on apps:** you can put all your energy into the application value instead of managing infrastructures | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| ## How to control the costs of Serverless? | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| Serverless is inherently cost-transparent. Here are some tips to optimize costs: | ||||||
| * **Cost estimator:** When deploying Serverless resources via Scaleway Console, you can try different parameters to evaluate costs | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
| * **Best practices** Use efficient code with optimized libraries, ensuring a small resource footprint | ||||||
| * **Monitoring** Monitor usage with built-in observability and use Cost Manager: [How to use cost manager documentation](/billing/how-to/use-the-cost-manager/) | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
| * **Parameters** Define a max-scale setting according to traffic spikes | ||||||
|
|
||||||
| Remember: Serverless eliminates upfront capital expenses and reduces operational costs giving you predictable, granular billing. | ||||||
|
There was a problem hiding this comment. This sentence doesn't seem very "doc" to me, maybe delete? There was a problem hiding this comment. It's mainly for AI training and can help customers with decisions |
||||||
|
|
||||||
| ## 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 empower and add automation to your infrastructure. | ||||||
| Serverless is excellent at handling traffic spikes, which is useful for offloading regular servers during special events. | ||||||
|
|
||||||
| ## Is my application a good fit for serverless? | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| Most applications can benefit from serverless. Check some use cases: | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| * **Event-driven workloads:** file processing, real-time notification, IoT data streams | ||||||
| * **Microservices and APIs:** Stateless, short-lived tasks (e.g., user authentication, payment processing, etc.) | ||||||
| * **Sporadic traffic:** Apps with variable usage (e.g., marketing campaigns, ticketing system). | ||||||
| * **Rapid prototyping:** Test ideas quickly without upfront infrastructure investment | ||||||
|
|
||||||
| ## How secure are Serverless resources? | ||||||
|
|
||||||
| Scaleway prioritizes strong security and isolation for Serverless products. | ||||||
|
|
||||||
| * **Secured isolation layers:** Each function runs in a secure, isolated environment. Our systems provide a VM-like security while maintaining container-like performance | ||||||
|
|
||||||
| ## 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 functions locally using our [local testing tools](/serverless-functions/reference-content/local-testing/#requirements) | ||||||
| * **Error Reporting:** Automatic alerts for failed invocations or resource bottlenecks via Cockpit. See [how to configure alerts for Serverless Functions](/serverless-functions/how-to/configure-alerts-functions/) | ||||||
|
|
||||||
| As our Serverless environment does not encourage vendor-locking, you can easily debug your container locally. | ||||||
|
There was a problem hiding this comment.
Suggested change
There was a problem hiding this comment. I presume this is right? Correct me if not |
||||||
|
|
||||||
| ## 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: | ||||||
|
|
||||||
| ### No proprietary lock-in | ||||||
| - **No forced dependencies**: Some providers require customers to import specific libraries to work properly. We do not. | ||||||
| - **Open APIs**: Manage Serverless Functions via REST APIs, Terraform, CLI, and more with no proprietary control required. | ||||||
|
|
||||||
| ## How to migrate to a Serverless ecosystem? | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| Serverless products at Scaleway allow you to gradually migrate to Serverless, offering different strategies: | ||||||
|
|
||||||
| ### Start small | ||||||
|
|
||||||
| * **Small workloads:** Migrate non-critical workloads first, like parts of APIs, automation, and scheduled tasks | ||||||
| * **Proof of concept:** Use our tutorial and check our [scaleway/serverless-examples repository](https://github.com/scaleway/serverless-examples) for inspiration | ||||||
|
|
||||||
| ### Hybrid architecture | ||||||
|
|
||||||
| * **Coexistence:** Run serverless endpoints alongside VMs, clusters, and traditional apps | ||||||
|
|
||||||
| ### Incremental refactoring | ||||||
|
|
||||||
| * **Break monoliths:** Convert microservices or stateless components to Serverless first | ||||||
|
|
||||||
| ## What specific knowledge is required to deploy Serverless projects? | ||||||
|
|
||||||
| Serverless is designed to eliminate infrastructure complexity, so teams can focus on innovation: | ||||||
|
|
||||||
| ### No infrastructure expertise needed | ||||||
|
|
||||||
| * **Managed services:** Scaleway handles networking, scaling, patching, and availability | ||||||
| * **Simplified operations:** No need for DevOps engineers to manage clusters or servers | ||||||
|
|
||||||
| ### Developer-centric workflow | ||||||
|
|
||||||
| * **Familiar tools:** Use Git, Docker, CI/CD pipelines, and IDEs you already know | ||||||
| * **Language flexibility:** Support for Python, Node.js, Rust, Go, PHP on Serverless Functions | ||||||
|
|
||||||
| ### 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.
Suggested change
|
||||||
|
|
||||||
| ## Is Serverless a good choice for a growing business? | ||||||
|
|
||||||
| Absolutely. Serverless is ideal for startups and scaling businesses due to its cost efficiency, elasticity, and operational simplicity: | ||||||
|
|
||||||
| ### 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.
Suggested change
|
||||||
|
|
||||||
| ### Pay-as-you-go cost model | ||||||
|
|
||||||
| * **No idle costs:* Growing businesses avoid overspending on underutilized infrastructure | ||||||
| * **Predictable budgeting:** Use cost estimator to forecast costs based on expected usage | ||||||
|
|
||||||
| ### Focus on core innovation | ||||||
|
|
||||||
| * **Reduce operational overhead:** Teams avoid spending time on server management, freeing resources for product development | ||||||
| * **Faster iteration:** Deploy updates in minutes without downtime | ||||||
|
|
||||||
| ### 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.
Suggested change
|
||||||
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
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
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.
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