add more content

Author: thomas-tacquet

pages/serverless-containers/reference-content/understanding-serverless-benefits.mdx

@@ -1,9 +1,9 @@
 ---
 meta:
-  title: Understanding Serverless benefits
+  title: Serverless ecosystem handbook
   description:
 content:
-  h1: Understanding Serverless benefits
+  h1: Serverless ecosystem handbook
   paragraph:
 tags: containers serverless
 dates:
@@ -28,24 +28,26 @@ Key features:
 * **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.
+Refer to the [differences between Functions, Jobs, and Containers](/serverless-containers/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.
-* **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.
-
+* **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
+* **Focus on apps:** you can put all your energy in application value instead of managing infrastructure
 
 # 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
+* **Cost estimator:** when deploying Serverless resources via Scaleway Console, you can try different parameters to evaluate costs
+* **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/)
+* **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.
 
@@ -58,27 +60,32 @@ You can fully deploy your API on Serverless or use it to emporer and add automat
 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
+* **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:** Apps 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.
+Scaleway prioritizes strong security and isolation for Serverless products.
+
+* **Secured isolation layers:** Each container 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 containers locally using the Serverless CLI and emulator
-* **Error Reporting:** Automatic alerts for failed invocations or resource bottlenecks via Cockpit
+* **Error Reporting:** Automatic alerts for failed invocations or resource bottlenecks via Cockpit. See [how to configure alerts for Serverless Containers](/serverless-containers/how-to/configure-alerts-containers/)
+
+As our Serverless environment does not encourage vendor-locking, you can easily debug your container locally.
 
 # 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:
 
@@ -87,5 +94,65 @@ We believe in empowering your freedom to choose, adapt, and evolve. Here is how
 - **No proprietary formats**: We don't modify your containers. What you build works anywhere.
 
 ## No proprietary lock-in
-- **No forced dependencies**
+- **No forced dependencies**: Some providers require customers to import specific libraries to work properly. We do not.
 - **Open APIs**: Manage Serverless Containers via REST APIs, Terraform, CLI, etc... no proprietary control required.
+
+# How to migrate to Serverless ecosystem?
+
+Serverless products at Scaleway allows you to gradually migrate to Serverless, different strategies are possible:
+
+## Start small
+
+* **Small workloads:** Migrate non-critical workloads first like internal APIs, automation jobs to Serverless Jobs
+* **Proof of concept:** Use our tutorial and check our [scaleway/serverless-examples repository](https://github.com/scaleway/serverless-examples) for inspiration
+
+## Hybrid architecture
+
+* **Coexistance:** Run serverless endpoints alongside VM, 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, and custom runtimes via Serverless Containers
+
+## 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
+
+# Is Servereless 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
+
+## 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