Migrating a Lightweight Web App to Serverless on Tencent Cloud: A Step‑by‑Step Guide

Serverless Overview

Serverless is a new type of internet architecture that drives cloud computing forward, from AWS Lambda to similar services from many vendors. It offers a "no‑server" model where developers focus on business logic while the platform handles infrastructure.

1. Serverless Introduction

This section briefly describes the evolution of Serverless, its definition, advantages, disadvantages, and suitable scenarios.

Cloud computing has progressed from IaaS, PaaS, SaaS to newer models like BaaS and FaaS, making Serverless increasingly prominent.

Key characteristics

Stateless: each function execution may run in a different container, so memory or data cannot be shared directly.

No operations: developers do not need to manage servers or infrastructure.

Event‑driven: functions are triggered by events.

Low cost: you only pay for execution time and memory usage.

Serverless combines Function as a Service (FaaS) and Backend as a Service (BaaS) to form a complete solution.

Serverless Advantages

Reduced startup cost

Lower operational cost

Decreased development cost

Fast release cycles

Accelerated CI/CD pipelines

Higher development speed

Improved system security

Fits micro‑service architecture

Automatic scaling

Serverless Disadvantages

Not suitable for stateful services

Unsuitable for long‑running tasks

Heavy reliance on third‑party services

Cold‑start latency

Lack of mature debugging and development tools

Typical Use Cases

Sending notifications

Webhooks

Lightweight APIs

IoT

Data analytics

Scheduled tasks

Lean startups

Chat bots

2. A Lightweight Web Application Migration Practice

This part demonstrates how to migrate a typical web application to Tencent Cloud Serverless Cloud Function (SCF), covering architecture changes, data storage, performance optimization, development workflow, and operations.

2.1 Architecture Migration

Static assets (JS/CSS/IMG/HTML) are stored in COS (object storage) with optional CDN acceleration. For single‑page apps, HTML can also be served by SCF, though using COS is more efficient.

API Gateway + application logic replaces the traditional Node server. The API Gateway event format can be parsed directly, or a proxy layer can translate the event into an HTTP request that a local socket forwards to a Node server, keeping compatibility with Express/Koa middleware.

Performance impact of the proxy layer is minimal; total function latency stays under 20 ms, with the proxy adding roughly 10 ms.

Available proxy frameworks include serverlessplus and scf-framework.

2.2 Data Storage

Because Serverless functions are short‑lived, persistent storage must rely on external services such as COS for files, Redis for caching, and a database (e.g., MySQL) inside a VPC for relational data.

Example npm command to install a Redis helper package: npm i qcloud - serverless - redis File storage uses the temporary /tmp directory (max 512 MB) which is cleared when the instance is reclaimed. For long‑term storage, use COS.

tnpm i @tencent/serverless-cos

2.3 Authentication

Login state can be maintained via third‑party services or JWT tokens. In mini‑programs, cookies are not available, so tokens are stored in localStorage and sent in request headers.

2.4 Performance Tuning

Cold start is the main latency source. Optimizations include:

Instance reuse (keep warm for 3 minutes to cover most cases)

Pre‑creating containers of various sizes

Caching hot code at node and data‑center levels

Predictive scaling using machine learning

Developer‑side optimizations:

Minify code to reduce download size

Separate common functionality into independent functions for better caching

Define shared resources (e.g., DB connections) outside the handler to avoid re‑initialization

Keep functions warm by periodic invocations

2.5 Development, Debugging, and Deployment

Three debugging approaches are described:

Cloud debugging (upload node_modules each time – cumbersome).

Local Docker debugging using tcf local invoke with a template and event file:

tcf local invoke --template template.yaml --event event/apigateway.json

3) Native local debugging with tcf native invoke which runs the function in the host environment, avoiding Docker mismatches.

Publishing can be done via the TCF CLI, either uploading a ZIP package (max 50 MB) or pushing code to COS. tcf package & tcf deploy Versioning is supported; functions can be copied to different namespaces for test and production environments, with environment variables distinguishing resources.

Namespace creation and function copying are performed through the console UI.

2.6 Domain Mapping

API Gateway provides a default domain, but custom domains (with HTTPS certificates) can be bound for a professional URL. Path mapping can also be configured.

2.7 Logging

SCF logs can be viewed in real time, filtered by request ID, and optionally routed to a dedicated Log Service for richer querying, indexing, and export to COS or CKafka.

2.8 Monitoring

SCF and API Gateway include basic metrics; for advanced dashboards, alerts, and custom business metrics, Cloud Monitor should be used.

Key Takeaways

Separate test and production using namespaces and versioning.

Deploy by copying functions and configuring environment variables.

Use function versions for safe rollbacks.

Future improvements in Tencent Cloud Serverless 2.0 aim to simplify CI/CD integration, reduce packaging overhead, and eliminate the need for an API Gateway proxy layer.