aa99afea2c
* General cleanup of sample and ref docs * move reference docs * fix nav and links * update redirects * fix comment * added Paul's script updates, updating ext versions |
||
|---|---|---|
| .. | ||
| broker | ||
| channels | ||
| configuration | ||
| custom-event-source | ||
| data | ||
| experimental-features | ||
| flows | ||
| images | ||
| observability | ||
| reference | ||
| sinks | ||
| sources | ||
| sugar | ||
| troubleshooting | ||
| OWNERS | ||
| README.md | ||
| accessing-traces.md | ||
| event-delivery.md | ||
| event-registry.md | ||
README.md
Knative Eventing
Knative Eventing is a collection of APIs that enable you to use an event-driven architecture with your applications.
You can use these APIs to create components that route events from event producers to event consumers, or sinks, that receive events. Sinks can also be configured to respond to HTTP requests by sending a response event.
Knative Eventing uses standard HTTP POST requests to send and receive events between event producers and sinks. These events conform to the CloudEvents specifications, which enables creating, parsing, sending, and receiving events in any programming language.
In a Knative Eventing deployment, event Sources are the primary event producers. Examples of sinks include Brokers, Channels, and Services.
Common use cases
Knative Eventing components are loosely coupled, and can be developed and deployed independently of each other. Any producer can generate events before there are active event consumers that are listening for those events. Any event consumer can express interest in a class of events before there are producers that are creating those events.
Examples of supported Knative Eventing use cases:
-
Publish an event without creating a consumer. You can send events to a broker as an HTTP POST, and use binding to decouple the destination configuration from your application that produces events.
-
Consume an event without creating a publisher. You can use a trigger to consume events from a broker based on event attributes. The application receives events as an HTTP POST.
!!! tip Multiple event producers and sinks can be used together to create more advanced Knative Eventing flows to solve complex use cases.
Eventing examples
:material-file-document: Creating and responding to Kubernetes API events{target=blank}
--8<-- "YouTube_icon.svg" Creating an image processing pipeline{target=blank}
--8<-- "YouTube_icon.svg" Facilitating AI workloads at the edge in large-scale, drone-powered sustainable agriculture projects{target=blank}
Next steps
- You can install Knative Eventing by using the methods listed on the installation page.