How Tencent CloudBase Transforms Serverless with Knative: From Functions to Containers

What is Serverless?

Serverless, also called "无服务计算" in China, is not a specific framework but a set of concepts that reduce operational overhead for developers. It is commonly expressed as Serverless = FaaS + BaaS.

FaaS (Function as a Service)

Major FaaS products include AWS Lambda, Azure Functions, Google Cloud Functions, and Tencent Cloud Serverless Cloud Function.

BaaS (Backend as a Service)

BaaS covers backend services such as databases, message queues, and storage, allowing developers to focus on business logic without managing infrastructure. DBaaS is a typical example.

Tencent CloudBase Serverless Practice

CloudBase provides a one‑stop multi‑terminal development platform that enables developers to quickly build business logic while the platform handles availability, reliability, and fault recovery.

To date, CloudBase serves 500,000 developers across mini‑programs, web, and native apps.

Challenges of Cloud Functions

Migration cost – existing services often require a resident backend, which conflicts with the event‑driven, on‑demand nature of functions.

Language ecosystem – each runtime (e.g., Node.js) must be kept up‑to‑date, and frameworks such as Koa or Express add additional adaptation effort.

Performance – cold‑start latency and limited ability to match traditional compute performance.

Serverless Cloud Applications

To address these shortcomings, Serverless Cloud Applications built on Knative are introduced.

Knative Overview

Knative, proposed by Google, simplifies Kubernetes usage and focuses on three components: Build, Serve, and Eventing.

CloudBase Serving

Each CloudBase service creates a URL that maps to one or more revisions (versions). Traffic can be split among revisions, enabling gray‑release strategies. Autoscaler adjusts replica counts based on request volume, and the Activator handles the 0→1 scaling.

CloudBase Build

Three deployment options are supported: image, source + Dockerfile, and source‑only. Image deployment pushes a Docker image to a private registry. Source + Dockerfile lets CloudBase BuildServer create the image in the cloud. Source‑only uses CloudBase CLI to build and deploy without a Dockerfile.

CloudBase Application Ecosystem

CloudBase applications integrate with existing CloudBase services (SDK, cloud calls, cloud payment). Static assets can be hosted separately, while dynamic logic runs in the cloud application under a unified domain.

Conclusion

By leveraging CloudBase, developers enjoy the operational simplicity of Serverless while avoiding the limitations of pure function‑as‑a‑service. Serverless Cloud Applications (CaaS) complement FaaS and BaaS, forming a new equation: Serverless = FaaS + CaaS + BaaS.