Este conteúdo não está disponível no idioma selecionado.
Chapter 1. Knative Eventing
Knative Eventing on OpenShift Container Platform supports event-driven architectures for serverless applications by decoupling event producers and consumers.
Producers create events, and sinks consume them. Knative Eventing uses HTTP POST requests to deliver events that follow the CloudEvents specification, which supports event handling across programming languages.
1.1. Knative Eventing use cases Copiar o linkLink copiado para a área de transferência!
Knative Eventing supports the following 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.
To enable delivery to multiple types of sinks, Knative Eventing defines the following generic interfaces that can be implemented by multiple Kubernetes resources:
- Addressable resources
-
Able to receive and acknowledge an event delivered over HTTP to an address defined in the
status.address.urlfield of the event. The KubernetesServiceresource also satisfies the addressable interface. - Callable resources
-
Able to receive an event delivered over HTTP and transform it, returning
0or1new events in the HTTP response payload. These returned events can be further processed in the same way that events from an external event source are processed.