Overview of event-driven processing based on Knative Eventing - Container Service for Kubernetes

Knative Eventing lets you build event-driven applications on Kubernetes without managing the underlying messaging infrastructure. Connect event sources — such as ApsaraMQ for RocketMQ, ApsaraMQ for Kafka, Container Registry, and EventBridge — to Knative Services or functions, and route events using the broker and trigger model.

Description

Knative Eventing meets the common needs in cloud-native development. In addition, Knative Eventing provides an architecture for serverless event-driven mode. The architecture contains event sources, event ingesting and subscription, and event filtering. The following figure shows the event-driven architecture.

Use scenarios	Description
Event sources	The Knative community provides a variety of event sources, such as Kafka and GitHub. Ingests events from message services such as EventBridge.
Event processing	Knative Eventing routes events from brokers to event sinks or consumers. You can create one or more triggers to filter or subscribe to specific events. Events can be consumed by serverless applications that are managed by Knative.
Event consumption	Automatically releases images in Container Registry upon updates. Automatically creates images upon code submission. Supports cron jobs and AI-assisted audio and video processing.

What's next

Deploy Knative Eventing through the console.
Send your first event with Knative Eventing to get started quickly.
Use EventBridge for event-driven architecture in Knative.