Serverless Introduction for Front-End Engineers

Serverless has become a hot term in the front‑end community in recent years, although it was first introduced seven years ago; this article defines what Serverless services are, outlines their architecture, and discusses their pros and cons.

Trend

According to the RightScale 2019 Cloud State Report, Serverless was the fastest‑growing public‑cloud service from 2018 to 2019, with a 50% growth rate, tying with Streaming Process for the top spot.

Google Trends also shows a steady rise in Serverless interest over the past two years, with China ranking first in regional heat maps, indicating strong enthusiasm and a promising future for the technology.

Concept

Serverless combines the words “server” and “less”, implying “few or no servers”. In practice it means developers do not need to manage hardware, operating systems, or stability; the cloud provider handles these concerns. Developers only write and upload functions, paying only for execution time. Mature Serverless products include AWS Lambda, Google Cloud Functions, Azure Functions, and Alibaba Cloud Function Compute.

Evolution

Before cloud computing, most compute resources were bare‑metal servers requiring costly hardware and network setup. With the advent of IaaS, users could rent virtual machines, offloading hardware management to providers. The rise of containers introduced PaaS and CaaS, allowing developers to focus on platform services and containers. Serverless pushes this further by abstracting execution to fine‑grained functions that run on demand, charging only for actual resource consumption.

Architecture

Serverless architecture consists of two parts: FaaS (Function‑as‑a‑Service) and BaaS (Backend‑as‑a‑Service).

FaaS provides a function execution platform where developers upload logic functions (e.g., scheduled tasks, data processing) and configure triggers and routing.

BaaS offers API‑based backend services such as databases, object storage, message queues, and logging, which the functions can call.

Serverless operates on an event‑driven model: a trigger (e.g., HTTP request) is received by an API Gateway, which passes parameters to the function platform; the function runs, optionally interacts with BaaS components, and returns a result. After execution, the runtime container is destroyed, ready for the next invocation.

Pros and Cons

Advantages of Serverless include reduced operational overhead, automatic scaling, pay‑per‑use pricing, and faster time‑to‑market.

However, Serverless also has drawbacks:

Vendor lock‑in : Using a public‑cloud Serverless product often ties you to other services of the same provider, increasing migration cost.

Not suitable for long‑running tasks : Execution time limits (e.g., 10 minutes on Alibaba Function Compute) require task splitting, adding complexity and possibly higher cost.

Cold‑start latency : Initial container startup can add delay, affecting response time.

Debugging and testing challenges : Differences between local and cloud environments increase development effort and testing expenses.

Use Cases

Given its strengths and limitations, Serverless is ideal for the following scenarios:

Scheduled tasks : Time‑triggered functions for routine business logic.

Data processing : Event‑driven pipelines for log aggregation, media transformation, etc.

Low‑frequency requests : Pay‑per‑use handling of infrequent API calls.

IoT : Event‑driven, low‑latency operations for device control.

Cognitive computing : Certain AI scenarios such as chatbots.

Conclusion

Serverless in China is still in its early stage, with many supporting services yet to mature and few large‑scale success stories. Nevertheless, front‑end engineers can benefit from Serverless by focusing on business logic while abstracting away infrastructure and operations, potentially accelerating development and enabling a shift toward full‑stack web application engineering.