Understanding Serverless: Concepts, Architecture, and Practical Deployment

When a sudden event or a brilliant idea arises, how can developers quickly turn it into a product? Serverless, a hot technology in cloud computing, offers a fast path to deployment. This article summarizes Wang Junjie’s talk at the "YunJia Community Salon Online," covering the basic concepts, framework principles, component architecture, and practical steps for using Serverless Framework.

1. Basic Concepts of Serverless

Serverless ("无服务器") does not eliminate operations but abstracts underlying resource management, allowing developers to focus on business logic. The term gained popularity after 2014, with major cloud providers releasing Function-as-a-Service (FaaS) products. Tencent launched SCF in 2017 and the Serverless Framework in 2019.

Three core factors drive computing technology: compute power, algorithms, and data. Cloud computing originally solved the problem of allocating compute resources efficiently. Serverless pushes this granularity down to the function level, enabling pay‑as‑you‑go billing.

2. Serverless vs. FaaS

FaaS is the execution‑granularity of Serverless: each function invocation receives its own compute allocation. Serverless = FaaS + BaaS (Backend‑as‑a‑Service), providing a complete platform that hides infrastructure details.

Key advantages include: Automatic resource provisioning and scaling Fine‑grained, per‑invocation billing (e.g., 1 ms granularity on Tencent Cloud) Reduced operational overhead for developers

3. From Prototype to Product

The transition involves three steps: business logic implementation, productization (performance, reliability, scalability), and operations (monitoring, logging, auto‑scaling). Serverless abstracts the lower‑level infrastructure, allowing teams to focus on the first two steps.

4. Full‑Stack Technical Layers

Four layers are identified: Core business logic (frontend, backend, API, data) Business architecture (frameworks, databases) Operations (logging, monitoring, load balancing) Underlying infrastructure (compute, network, security) Serverless primarily addresses layers 2‑4, letting developers concentrate on layer 1.

5. Serverless Framework Principles

The framework should be componentized and standardized. Components are npm modules configured via YAML, allowing reuse across teams and cloud providers.

6. Serverless Framework Overview

Serverless Framework provides a unified CLI, component library (e.g., Express component), and full lifecycle management from development to production.

7. Practical Deployment Steps

To deploy a Serverless application: Install the Serverless CLI Configure a serverless.yml file (YAML) Deploy with sls The CLI handles resource provisioning, CDN, security, monitoring, and can remove everything with sls remove .

8. Standardized Development Mode

Serverless integrates with DevOps platforms (e.g., CODING), offers a Dashboard for resource management, and supports advanced monitoring and alerting.

9. Q&A Highlights

Key questions addressed include the relationship between Serverless and GraphQL, cold‑start concerns, suitability for high‑concurrency scenarios, and the role of traditional backend skills.

Overall, Serverless is presented as a future direction of cloud computing that empowers developers across front‑end, back‑end, and full‑stack roles.