Master Knative Serverless: Serving, Eventing, and Alibaba Cloud Integration

Knative Overview

Knative is an open‑source serverless application orchestration framework built on Kubernetes. It provides a standardized way to run serverless workloads, combining a native workflow engine and a full event system.

Core Modules

Knative consists of two main modules: Serving for deploying and managing workloads, and Eventing for event‑driven architectures.

1. Serving – Serverless Service Engine

Serving offers a simple, efficient application hosting service. It automatically scales pods up or down based on request volume, enabling cost‑effective operation.

Key capabilities include traffic management and progressive rollout (gray release) based on percentage splits.

Knative Service abstracts the deployment model as: Knative Service = Deployment + Service + Ingress The Service resource creates a hierarchy of objects:

Service : manages the application lifecycle.

Configuration : stores the desired state; updating the Service creates a new Configuration.

Revision : a snapshot of each Configuration update, used for versioning.

Route : routes traffic to specific Revisions, supporting percentage‑based splits.

Serving also provides built‑in traffic splitting and gray‑release capabilities, allowing fine‑grained control over which Revision receives what proportion of traffic.

2. Eventing – Serverless Event‑Driven Framework

Eventing supplies a complete event model that can ingest external events and forward them internally using the CloudEvents standard.

Two forwarding patterns are supported:

Directly forward events from a source to a Service.

Forward events to a Broker/Trigger, then filter and route them to Services.

For event sources that require buffering or reliable delivery (e.g., GitHub, K8s API server), the Broker/Trigger model is recommended. For sources that are already message systems (e.g., Kafka, RocketMQ, MNS), direct forwarding is more efficient.

Knative ships with a variety of built‑in sources such as Kafka, GitHub, and can be extended to cloud‑native message services like Alibaba Cloud MNS.

Alibaba Cloud Integration

Alibaba Cloud extends the upstream Knative project by tightly integrating with its own product ecosystem, adding richer capabilities and enterprise‑grade support.

Key integrations include:

Message services: Kafka, MNS, RocketMQ as event sources.

Service access via SLB.

Storage options: NAS, cloud disks.

Observability: Log Service, ARMS.

Compute resources: ECS, ECI.

Alibaba Cloud also offers a fully managed Knative control plane on its Serverless Kubernetes (ASK) offering, reducing operational overhead.

Practical Example: Real‑Time Bullet‑Screen Service

The following example demonstrates a complete workflow for a bullet‑screen (danmaku) application.

Architecture diagram:

Step‑by‑step flow:

User sends a bullet message to a web service, which writes it to Alibaba Cloud Kafka.

A Kafka Source in Knative Eventing consumes the message and forwards it to a processing service.

The processing service scales automatically (KPA/HPA) to handle the load, processes the message, and forwards the result to the bullet‑screen service.

The bullet‑screen service renders the message on the web UI for the user.

Conclusion

Alibaba Cloud Knative delivers low‑entry‑barrier service deployment, on‑demand resource usage, seamless event‑driven integration with Alibaba’s messaging products, native compatibility with the Alibaba Cloud Kubernetes ecosystem, and deep product integration, all of which help reduce operational and resource costs while embracing the serverless philosophy.