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

Knative Eventing provides an event model, which can be used to interface with external event systems, such as GitHub, ApsaraMQ for RocketMQ, ApsaraMQ for Kafka, and Container Registry, and route events to Knative Services or functions for processing. Knative Eventing supports a wide range of event sources. It processes events based on the broker and trigger model, and can be used in diverse event consumption scenarios, such as AI audio and video processing, scheduled tasks, and direct image building upon code commits.

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 Simple Message Queue (formerly MNS) (SMQ) and RocketMQ.
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 vidoe processing.

What to do next

To deploy Knative Eventing through the console, see Deploy Knative Eventing.
To use Knative Eventing with different event sources, see Use Knative to manage GitHub events, Use Knative to manage MnsOss event sources, and Use EventBridge to trigger Knative Services to consume events.